1. Enter Registered Email Address: Start by entering the Admin registered email address in the designated field. [1]

Click “Verify”: Click the “Verify” button to validate the Admin email address. 

– If the email is valid, Admin will receive a “Set Password” link in the Admin registered email inbox.

Note: If Admin does not receive the email, check the email you entered or please try another email address or contact a CRM-authorized person for assistance.

1. Check the registered Email: Access the registered email account, check the “Set Password” email sent to the Admin , and click on the link provided in the message. [1]

2. Create a New Password: Clicking the link will redirect the Admin user to the “Create New Password” page, where they can enter and confirm their desired password to complete the setup. [1]

1. Enter New Password: On the “Create New Password” page, type the desired new password in the “New Password” field. [1]

2. Confirm Password: Re-enter the same password in the “Confirm Password” field.  [1]

Click “Save”: After entering and confirming the password, click the “Save” button.

If successful, Admin will be redirected to the Admin login screen.

1. Enter Login Credentials: On the Admin login page, enter the registered Admin email address and the password set via the link sent to the registered email.

2. Click “Login”: If the credentials are correct, the Admin will be redirected to the Dashboard.

– Forgot Password: If the Admin has forgotten their password, click the “Forgot Password” link.

1. Enter Registered Email Address: On the “Forgot Password” page, enter the registered Admin email address and click the “Send” button.

– If the email is valid, a “Password Reset” link will be sent to the Admin ‘s registered email. [1]

2. Click the Reset Link: Click the link in the email to be redirected to the “Create New Password” page.

– Follow the instructions in Step 3- Create a new password to set a new password. [1]

Note: The password reset link will only be sent to the registered email address associated with the Admin account. If the Admin does not receive the email, please contact a CRM-authorized person for assistance.

Once the admin successfully logs into the Admin Portal, the admin first needs to set up the SMTP  configuration for email.

Authentication Type: First, the admin needs to select the Authentication Type according to the requirement. 

1. Credential/App Password: In this option, admin needs to enter a username and password for specific apps like social media, Outlook, Gmail, Apple Mail, etc.

2. Google OAuth: Auth is a security protocol that allows applications to access admin data without requiring passwords. This is integrated with Google services like Gmail, Google Calendar, Google Contacts, etc.

1. Credential / App Password

In this option admin enters the selected app Email ID and password (for ex: Outlook, Gmail, Apple Mail, etc.)

– For example: Admin uses the Gmail ID and Password for SMTP configuration. [2]

To establish a reliable connection for sending emails admin needs to add the following details: 

– From Name:  Enter the name that admin wants to display in the receiver’s Email.

– From Address: Enter the email address that the admin wants to display in the receiver email.

– SMTP Host: Enter the host address of email.

– SMTP Port: Enter the port number used by outgoing mail servers.

– Username: Enter the app username/email.

– Password: Enter the password of the email/username entered above.

Note: The admin has the flexibility to use any set of credentials for the SMTP configuration, regardless of the credentials used to log into the admin portal. This allows the admin to choose credentials freely without being restricted to the ones used for portal access.

After entering the details click on the “Save” button.

2. Google OAuth

In this Authentication type, the admin can connect Google Account with the portal by entering Client ID and Client secret. [3]

– Client ID: Enter admin client ID. Click on the Link to generate a Client ID.

– Client Secret: Enter admin client secret. Click on the Link to generate a Client Secret.

After entering the ‘necessary’  details, click on the “Save” button to complete the SMTP settings. 

Test Email Connection:

Send Test Email:  Click on the “Send Test Email” button to initiate a test of the SMTP connection.

Click Sent Mail: In the popup box, the admin should enter the recipient’s email address and a description, then click the “Send Mail” button. [4]

Connection Status

Connected: If the test email is received successfully on the above-entered mail, then the  SMTP configuration has been established correctly.

Not Connected: If the email is not received, the admin should verify that all SMTP configuration details—such as the SMTP Host, Port, Username, and Password—are entered correctly or not.

Note: Each SMTP server has different authentication methods, so the admin must follow the specific rules of their mail server.

Popular SMTP Server Configurations 

– Microsoft Exchange:

Server: smtp-mail.outlook.com

Port: 587

– Yahoo:

Server: smtp.mail.yahoo.com

Port: 587

– Gmail:

Server: smtp.gmail.com

Port: 587

– Hotmail:

Server: smtp.live.com

Port: 587

– AOL:

Server: smtp.aol.com

Port: 587

Please note that these configurations are commonly used,  but the admin should always check with the respective email service provider for the most current and accurate SMTP server settings

After setting up the SMTP configuration, the admin must configure CRM authentication to connect CRM data with the Portal.

To do this the admin should navigate to Settings > Portal Setting > CRM Authentication. [01]

To access the CRM authentication screen, the user must validate their identity through the OTP verification process.

OTP Verification: On the CRM authentication page admin will see an  OTP verification screen.  The admin needs to enter the OTP received on the registered email ID. [1]

Note: Only super admin receives the OTP, on their registered mail Id.

Once the verification process is complete then the admin needs to configure the CRM authentication by  entering the  following details: [2]

– Authentication Type: Choose the authentication method for Salesforce, either Credentials or JWT.

Credentials: Information like a username and password used to log in.

– Example: Admin logs into the CRMJetty portal by entering their username and password.

JWT (JSON Web Token): A secure token that stores user data and is used to keep sessions active.

– Example: After logging in, Admin uses a JWT to make secure API calls without needing to log in again.

– Environment: Select the CRM environment—Live or Sandbox—to connect the CRMJetty Portal. [3]

Credential-Based Authentication:

For Credentials authentication, the following details are required:

– Client ID: Enter the Client ID for your selected environment.

– Username & Password: Enter the portal credentials.

– Security Token: Enter the security token from the relevant environment (Live or Sandbox).

– Client Secret: Enter the Client Secret key.

After configuring the credentials authentication click on the “Save” button  to complete the CRM Authentication process.

JWT-Based Authentication:

For JWT authentication, enter the following details:

– Client ID: Insert the Client ID generated by JWT.

– Username: Enter the portal credentials.

– Public Key: Insert the Public Key generated by JWT.

– Private Key: Insert the Private Key generated by JWT.

 After entering the required details, click on the “Save” button to complete the CRM Authentication process.  [5]

Test CRM Connection

Test connection: By clicking on the “Test Connection” button the portal verifies whether the entered credentials are correct or not. [6]

Connection Status:

Connected: If the connection is successful, then the admin can see the success token message on the right side of the page. [7]

Not connected: If the connection is unsuccessful, the admin should verify all the details  – such as the service URL, App ID and Client Secret – are entered correctly. If the issue persists, the admin should contact the CRM authorized person for further assistance.

Preserve & Reset Data

The Admin can modify the entire CRM structure if needed. In this case, there are two options available: Preserve Data or Reset Data.

Preserve Data:

This option retains the design structure but removes CRM-specific data for the new portal. All pages, forms, lists, menus, and sites will be preserved. However, the Admin will need to reconfigure certain elements, such as:

Lists, Forms, and Widgets containing CRM-based settings like Recent Activities, Counters, and Data Cards.

Roles from the previous CRM will be transferred to the new CRM, but since the object and user relationships will differ, access rights will need to be reassigned. Although the role and contact data will be preserved, they will not be connected to the newly authenticated CRM.

Additional considerations in Preserve Data:

– Layouts will remain as they are, ensuring that your portal design is preserved.

– object data will be different because the CRM data and connections are not carried over.

– User and relationship data from the previous CRM will not apply to the new CRM setup. Roles and contact relations from the old CRM will remain, but their connection to the new CRM will not be established.

– If roles from the old CRM were connected to the new CRM, they will have different role IDs and permissions in the new instance.

Reset Data:

This option clears all data from the portal, removing pages, forms, lists, templates, and site configurations. The admin will start with a clean slate, needing to set up everything from scratch, including layouts, widgets, and CRM connections.

Scenarios to Consider

Fresh Instance (No CRM Authenticated):

If there is no prior CRM authenticated, successful authentication of the CRM will result in the creation of:

– A default role connected to contact relations.

– Access to the case object.

– Default pages, lists, and forms such as Registration, Login, Forgot Password, and basic CRUD pages for the objects .

New Instance (CRM Authenticated):

If a CRM is already authenticated and the Admin attempts to change the CRM, a warning popup will appear, informing the Admin about the upcoming changes. The Admin can choose between Preserve Data or Reset Data.

Upon successful authentication, all data from the Role object will be cleared, and portal access will be removed from existing contacts.

Layouts and configuration will be preserved if ‘Preserve Data’ is selected, but the relationships between objects  will need to be reassigned.

Change in Current Instance:

 When changes are made to the Service URI or Organization ID, the portal will automatically detect this and issue a warning. Based on the Admin’s choice to preserve or reset, all portal data—including layouts and configurations—may be removed.

The Super Admin can assign multiple roles to sub-Admin , each with different responsibilities. To create a role, navigate to Settings > User Settings > Admin Roles. [1]

Note: These roles apply only to the admin portal. Both Super Admin  and sub-Admin  with Admin role permissions can add new roles.

On the admin role page admin can view Role Name and Status. On the right side of the page admin can view the “+Create” button. By clicking on the button admin can add a new admin role for the admin portal. [2]

Creating a New Role

On the “Add Role” page, the admin needs to enter below details:

1. Role Name: Enter a unique name for the sub-admin role.

2. Status: Click on the toggle button to set the role as “Active” or “Inactive.”

3. Description: Provide a brief description of the sub-admin role for future reference. [3]

4. Permissions: Select the checkbox next to each  object and set the permissions for  View, Add, Edit and Delete actions.

The sub-admin access to specific objects  will be determined by these permissions. [4]

Note: Sub-admin users can only access the objects  that the super admin has allowed.

Edit Admin Role:

To edit an admin role, navigate to the admin role list and click the three dots (…). This will reveal the Edit icon. Clicking the icon will redirect the admin to the edit role page. [5]

On the Edit page, the admin can modify the role’s name, status, description, and permissions as needed. [6]

 After making the changes, click the “Save” button to apply the updates.

Delete Admin Role:

To delete an admin role, go to the admin role list and click the three dots (…). Click the delete icon, and a pop-up will appear. [7]

In the pop-up click on the “Ok” button to permanently delete the role from the portal or  click on the “Cancel” button to keep the role. [8]

The Super admin can add multiple sub-admin users for different responsibilities. To do so navigate to Settings > User Setting > Admin Users Setup. [1]

Note:. This setup applies only to the admin portal.   Super Admin  and sub-Admin  with Admin user setup rights can add new users.

Admin User Card: On the admin user page, the admin will be able to see the card view with the below-mentioned details. [2]

– Name

– Role

– Email Id

– Last login information 

The Super admin can assign different roles  to various sub-admin users. To add a new sub admin follow these steps: 

– Create New User: Click on the “Create” button to add a new admin user. [3]

– Enter User Details:  By entering the following details super admin can configure the sub admin user.

– Name: Enter a unique name for the sub-admin user.

– Email: Enter a registered email ID for sub-admin.

– Phone No: Add a support contact number for assistance. (Optional) 

– Status: Click on the toggle button to set the user as “Active” or “Inactive.”

– Photo: Upload the profile photo for identification. (Optional)

– Roles: Select a role for the sub-admin from the drop-down menu. [4]

Note:  The super Admin can create roles from the “Admin Roles” panel, and any roles created there will appear in the Roles drop-down. By default, the ‘Admin ‘ and ‘Sub-Admin ‘ roles are available.

Note: Sub-admin users who have rights to add a new user can only add users. Sub-Admin  with the rights to add new users can only add users and cannot modify their own permissions.

Edit Sub-Admin User 

To update a sub admin’s details, click the three dots (…) in the card view, click on the “Edit” icon to be redirected to the edit page. [5]

Here admin can view the “Edit” button by clicking on the edit button, admin is redirected to the edit page. [6]

Note: The Super Admin cannot modify the sub-admin’s email address during editing.

Admin can customize the portal’s name, logo, and favicon through the General Settings. To do this, navigate to Settings > Portal Settings > General Settings. [1]

Admin can set the admin portal by entering the following details. [2]

– Portal Name: Enter the name of the admin portal.

– Portal Logo: Upload a logo that will be used for the admin interface and displayed in the top left corner.

– Portal Favicon: Upload a favicon that will be shown in the browser tab for the Admin interface.

Admin can customize the theme colors, font style, and font colors by navigating to Settings > Portal Setting >  Admin Theme Customization [1]

Additionally, admin can adjust the following elements:

Customize Theme Elements:

– Base Font Family: Choose a font for the main body text and menus.

– Title/Heading Font Family: Choose a font for all the headings and titles throughout the portal. [2]

Color Customization:

– Theme Background Color: Choose a background color for the overall body of the portal.

– Foreground Color: Select a background color for content areas.

– Primary Color:  Choose a primary color used throughout the portal, including text and icons.

– Success Color: Select a color to indicate successful actions (e.g., toast notifications).

– Danger/Fail Color:  Choose a color for failed actions or errors (e.g., toast notifications).

– Warning Color:  Select a color for warnings (e.g., toast notifications).

– Base Font Color: Choose a color for the body text and main content descriptions.

– Link Color: Choose a color for all text links.  

Click the Save button to apply the theme and font updates.. To revert the theme settings, click the Default Theme button. [3]

The Portal Sync feature ensures that the CRMJetty admin portal stays updated with the latest data from the admin CRM system. Whenever the admin updates objects or modifies specific data within the CRM, it’s essential to synchronize with the portal to ensure consistency.

Admin  can perform synchronization through various options, such as Object Level Sync for syncing CRM data at an object level, or Portal-Level Object Sync to synchronize specific portal objects. Additionally, they can choose to Sync All Objects at once or Sync Specific Objects as needed. For a more detailed synchronization, Box Level Sync is available for specific data structures.

To access these options, the admin should navigate to Settings > Portal Settings > Portal Sync. [1]

Portal Sync Options:

On the Portal Sync page, the admin has access to three key synchronization options: 

1.  Object Level Sync 

2. Portal-level  Object Sync

     – Sync All objects 

     – Sync Specific object

3. Box Level Sync 

1. Object Level Sync

 If you have made any changes at the object level from CRM.

The Admin should use this “Object  level Sync” option if the admin modifies the structure or any objects  (like accounts, contacts, leads, etc.) in the CRM system. 

If the admin performs such operations as adding new fields, modifying existing ones, or even deleting fields. So the admin needs to use this object sync option.

The admin can perform the object level sync by clicking on the “CRM Sync” button that is shown in the screenshot. [2]

Once the object syncs successfully, the admin can view the success toggle message on the right side of the page as shown in the screenshot. [2.1]

2.  Portal-level  Object Sync

If admin have made any changes at the object level (portal level objects) from CRM

When the admin modifies objects  or any specific fields in the CRM system then the admin needs to sync those objects  or fields to the portal using “Portal Level object Sync”.

In this sync option, the admin has the advantage of syncing the data in two ways: [3]

Sync All objects :  In this option, the admin can sync all object -level data to the CRMJetty portal. All objects  are updated with just one sync. 

The admin needs to select the “Sync All objects ” radio button and click on the CRM Sync button as shown in the screenshot [4]

Sync Specific object: In this option instead of syncing all the objects , the admin can choose a specific object (like accounts or contacts) to sync. This is useful when changes are limited to one or a few objects , allowing the admin to update only what’s necessary without affecting other data.

By clicking on the “Sync Specific object” radio button the admin can see the “select object sync” drop-down where the admin needs to select the specific object, that they want to sync with the portal and after that click on the “CRM sync” button as shown in the screenshot.[5]

Note: The sync might take a few minutes. Please don’t log out or make any changes in the CRM system during this time.

3. Box Level Sync

If admin have made any changes at the box level from CRM

The Admin should use this “Box level Sync” option if the admin modifies the structure or relationship changes in the CRM system.

If the admin performs such operations as adding new fields, modifying existing ones, or even deleting fields. So the admin needs to use this object sync option.

The admin can perform the object level sync by clicking on the “CRM Sync” button that is shown in the screenshot. [6]

Once the object syncs successfully, the admin can view the success toggle message on the right side of the page as shown in the screenshot. [7]

The CRMJetty portal allows the admin to manage various email templates for different actions . To configure these templates, the admin should navigate to Settings > Portal Setting > Email Templates. [1]

On the email templates page, the admin can view by default created templates.  The admin can modify the default templates or create a new one.  [2]

CRMJetty portal provides 8 types of email action templates as follows:

1. Admin User OTP: Sends a One-Time Password  (OTP) to the admin for secure login.

2. Approve Portal User: Notifies the user that their portal access  has been approved.

3. Forgot Password: Send a link to reset the user’s password. (Send a link to the user to reset their password.)

4. Forgot Username: Help the user recover their username via email.

5. Registration: Confirm the user’s registration and next steps.

6. Send Email to From Respondent: Forward the respondent’s email to the recipient.

7. Two-Step Verification: Sends a verification code for two-step authentication.

8. Verify Portal User: Confirms the user’s id object verify their portal account.

Create New Template :

To add a new template, click on the Create button and the admin will be redirected to the Create email template page. The admin can add multiple templates for a single action. [3]

The Admin needs to enter all the required details which are mentioned below:[4]

– Name: Enter a template name to identify the email action.

– Subject: Enter the subject of the email.

– Status: Set the template as ‘Active’ or ‘Inactive’.

– Email Action: Select the action from the drop-down menu. Below mentioned is a list of the dropdown menu.

   – Admin User OTP

   – Approve Portal User

   – Forgot Password

   – Forgot Username

   – Registration

   – Send Email to Form Respondent

   – Two Step Verification

   – Verify Portal User

Note: The email actions are pre-defined, super admin can not add more action in the drop-down.

Body: In the email body the admin needs to write the email content also the admin can use editing options for formatting. 

Admin needs to enter the required parameters in the description box that is shown below the email body.

 Note: Based on the email actions the parameters will be shown.

For example: Admin creates a new template for “Approved Portal User” then the admin is required to add the following parameters. [4]

– [FULLNAME]:  It will be replaced with the portal user’s “First Name”.

– [EMAIL]: It will be replaced with a user email ID.

– [PORTALNAME]:  It will be replaced with Portal Name.

Note:  For each action, there are different parameters admin required to include all mandatory parameters in the template.

After entering all the data, the admin needs to click on the “Save” button then the admin can see one pop-up message that “old email will be inactive once the admin activates this template.” 

If the admin clicks “OK,” then the old email template will automatically be deactivated, and the new template will be activated.  [5]

Note: If admin creates a new template for the same action, the previous template will automatically become inactive. Admin users can select the templates in the Form widget configuration.

Edit template

The admin can modify the default email templates by clicking on the three dots (…). By clicking on the dots the admin can see the Edit button and once the admin clicks on the Edit button then they are redirected to the Edit Template Page. [6]

On the edit page, the admin can edit the Name, action, subject and description. [7]

Note: The admin cannot edit the email action type and status while editing the template.

Delete Template:

If the admin wants to delete the email template, the admin needs to click on the three dots (…) on the email template listing page. By clicking on the dots the admin can see the Delete button and by clicking on that they can see one warning (pop-up) message. [8]

In the pop-up click on the “Ok” button to permanently delete the template from the portal or else click on the “Cancel” button to keep the template. [9]

Note: The admin can only delete active templates from the portal.

The admin can design a “Form” and “List” for the portal users from the Portal User Settings. This Form and List will be shown to the users who are added by the admin from the backend.

By using this form, admin can directly add portal users from the backend.

To design a List and Form the admin will navigate to Settings >  Portal Setting >  Portal User Settings [1]

Note: The form and list will be displayed in the admin backend only. 

List Page:

The admin can see all the “List” fields on the right side of the page, to create a “List” the admin can search for fields or simply drag and drop them to the page. The admin only adds the 5 fields to design a list. [2]

Note: The admin cannot remove the required fields. If the admin is trying to remove it, they have shown a toggle message on the right side of the page.  

Form Page:

The Admin can add/Edit the portal user form for the customer portal, for that click on the Add/Edit radio button which is highlighted on the image. [3]

To design a form the admin can follow Add Section > Add Grid > Add Fields.

Add Section: On the left side of the page, the admin can view the sections and by clicking on the “+” icon the admin can add a new section as shown in the mentioned screenshot. [4]

Add Grid: After adding the section the admin needs to select the grid, for that, the admin needs to click on the “Add Grid” button as shown in the mentioned screenshot. [5]

By clicking on the button, the admin can view the different grid options, when selecting the grid it will directly add to the selected section as shown in the below screenshot. [6]

Add fields: After adding the grid the admin adds fields to the grid, the admin needs to drag and drop the fields to the section as shown in the screenshot. [7]

Note: The grid supports only one field per box. Admin should ensure the sections are designed accordingly.

Once the form design is complete the admin needs to click on the “Save” button.  The admin can also view the form by clicking on the “Preview” button. [8]

Preview: 

When the Admin adds a portal user through the Admin Portal, the configured form and list will be displayed.

To view form and List Navigate to the Settings > User Setting > Portal User Setup section, where the Admin can view the form and list that have been previously configured. [9] [10]

Admin can set permissions that determine what actions portal users can perform and what information they can access within a system.

To role for the portal user navigate to Settings >  User Setting >  Portal User Roles. [1]

Creating a Role:

On the portal user role page, the admin can view the pre-existing “Default” role which is set up with standard permissions and access controls. [2]

Admin can modify that default role or add a new role, To add a new role admin needs to click on the “Create” button. [3]

By clicking on the create button the admin will be redirected to the “Add Role” page where they can see the below-mentioned fields.

– Role Name: Enter the name for the role.

– Status: Select the status role “active” and “inactive”.

– Is Default: Enable this toggle to set this role as a default.

– Description: Provide a short description for the role.

Object Permissions:

After adding basic details, the admin can manage object permissions for portal users by defining their roles. To define the role the admin needs to follow below steps:

– Object name: Admin can view the CRM portal object names.

– View: By clicking on the “View” checkbox admin allowed the portal user to view this particular object.

– Relationship Type: The admin can set the relationship type for the portal user based on the following four options:

1. Contact: Relationship with individual contacts.

2. Account: Relationship with specific accounts.

3. Account to My Records: Relationship with accounts linked to the admin’s own records.

4. Account with All Records: Relationship with accounts that have access to all records. [4]

Relationship Type: A relationship type in CRMJetty defines how a portal user is connected to and interacts with data, such as contacts or accounts, within the system. It determines the level of access and visibility the user has to specific records based on their role and association, such as individual contact records or broader account-based records. [5]

– Contact: Portal users can only access data related to their individual contact profile.

– Account: Portal users can view and manage records tied to their associated account.

– Account with My Records: Portal users can access their individual records within the associated account.

– Account with All Records: Portal users can view and manage all records within their associated account, including other users’ records.

Contact Relationship: It refers to how a portal user interacts with data based on their individual contact profile. This type of relationship limits access to records or data directly linked to the user’s contact, allowing personalized data access. [6]

Account Relationship: It defines how a portal user interacts with data based on the organization or account they are associated with. Instead of limiting access to personal contact data, it allows users to access data related to their entire account, which may include other users or records linked to that account. [6]

– Add: Click the checkbox to allow portal users to add data.

– Edit: Click the checkbox to allow portal users to edit data.

– Delete: Click the checkbox to allow portal users to delete data.

– Enable Product: Click the checkbox to allow portal users to product-related actions.

– Enable Hierarchy: Click the checkbox to allow portal users to have hierarchical permissions. [7]

Documents Permissions: Document Permissions in CRMJetty define the level of access and control portal users have over documents and files within the portal. The Admin can set specific permissions to regulate what actions users can perform, such as viewing, adding, deleting, or managing files and folders. Each permission type allows the Admin to tailor document access according to the user’s role in the portal. [8]

– Object Name: The admin can view the names of CRM portal objects .

– Documents: Click the checkbox to allow the portal user to manage files and folders within the portal.

– Document Access: Click the checkbox to grant the portal user permission to access and view documents.

– File Add: Click the checkbox to give the portal user permission to upload new files.

– File Delete: Click the checkbox to give the portal user permission to delete existing files.

– Folder Add: Click the checkbox to allow the portal user to create new folders.

Editing & Deleting Roles:

Edit Role:

– To edit a portal role, navigate to the portal role list and click the three dots (…). This will show the Edit icon. Clicking the icon will redirect to the edit role page. [9]

– Admin can update all the details and after updating the details click on the “Save” button.

Delete Role:

– To Delete a portal role, navigate to the portal role list and click the three dots (…).  [10]

– By clicking on the dots the admin can see the Delete button and by clicking on that they can see one warning (pop-up) message. [11]

– Click on the “Ok” button and the role will be permanently deleted from the portal.

Note: Default roles cannot be deleted.

Replace Role:

– The admin can replace a role assigned to users (contacts) with another role from the list of portal user roles.

– To replace the role the admin needs to click on the “Replace Role” icon from the (…) dots. [12]

– Then one pop-up will appear that allows the admin to select a new role from the drop-down list. Once the admin chooses a new role, it will replace the current role and be assigned to all contacts (portal users). [13]

Set as Default Role:

– The admin can set the default role with another role from the list of portal user roles.

– To set a default role, the admin needs to click on the “Default Role” icon from the (…) dots. [14]

– When the default button is clicked, a warning pop-up will appear with the warring message. Admin can either click “OK” to confirm, which will replace the default role with the selected one, or click “Cancel” to keep the current default role unchanged.

– After the default role is changed, the Admin can view the “Is Default” status set to “Yes”. [16]

Portal User Setup involves configuring and managing settings for users who access the portal. This setup ensures that users have the appropriate access, permissions, and functionality needed for their roles within the portal.

To manage a portal users the admin will navigate to Settings > User Setting >  Portal User Setup. [1]

On the Portal user setup page, the admin can view contact information which is created in the below-mentioned ways, 

  – Contact created from the CRM

  – Contact created from the Admin portal

  – Contacts that are registered from the Website.

To create a new contact from the Admin portal the admin needs to click on the “Create” button. [2]

Create Contact:

– After clicking on the “Create” button admin will be redirected to the Create Contact page.

– Enter the Portal Contact Details

Note: The “portal contact details” form will be shown as per the admin created in the portal user settings. [3]

– The admin needs to enter all the mandatory details to create a contact.

Note: If the admin won’t select any role from the “Role” lookup list, so the contact will be created as “Default”

– Once the admin fills all the information then they need to click on the “Save” button. By clicking on the save button the created contact will not receive any verification link.   

Note: If saved as Not Approved, the admin can later approve and generate credentials from the contact’s listing page.

– If the admin clicks on the  “Save & Generate credential option”, so the created contact will receive an email with the verification link. [4]

Bulk Update

1. CRMJetty Portal Approval: If the ‘User approval’ flow is enabled then admin approval is required after registration. Consider the below cases for approval.

– Case-1: The admin needs to select the Contact from the list manually (they can select one or multiple contacts) and click on the bulk action checkbox so they will be able to see the Approve button to send the verification link the admin needs to click on the approve button. (credentials pending). [5]

– Case-2: Select Approved and click Save & Generate Credentials to approve and generate credentials, sending an access link via email. [6]

Note: Only admin users with access can add contacts.

2. Enabling Portal Users: To give contacts access to the portal, the admin can use the ‘Enable’ option to approve the portal user.

Generate Credentials:

– The admin needs to select the Contact from the list manually. [7]

– Use the Bulk Action drop-down menu to select “Enable” for the contacts. This can include both newly added contacts and those previously disabled.

– After clicking the “Enable” button, a pop-up will appear. In this pop-up, the Admin needs to select the role to assign the same role permissions to the user. Once the role is selected, click the “Save” button. [7.2]

– In the compilation process, a popup will display the summary report for below-mentioned detail. [7.3]

  – Selected User

  – Disabled Users

  – Conversion Pending

3. Disabling Portal Users: With use of this feature admin can temporarily remove portal access by disabling user accounts.

– To disable the accounts, Admin needs to Select the contacts that need to be disabled from the portal.

– From the Bulk Actions drop-down menu, select “Disable.” button [8]

– A popup will display the summary report for below-mentioned detail. [9]

  – Selected User

  – Disabled Users

  – Conversion Pending 

4. Assigning New Roles : If an admin needs to assign a new role to contacts then they can use the “Role New Assign” option. 

– The admin needs to Select the contacts that need to assign a new role.

– From the Bulk Actions drop-down menu, select “Assign New Role.” [10]

– Click “Apply” to open the Assign New Role popup. 

– Choose the new role the admin wishes to assign. [11]

– Click “Save” to assign a role for the selected contact. [12]

5. Sending Password Link: The admin uses this option to send a password reset link to contacts so they can update their credentials.

– The admin needs to Select the contacts that need a password reset link.

– From the Bulk Actions drop-down menu, select “Send Password Link.” [13]

 -A popup will appear showing the status of the password link delivery status.

Edit Contact:

To edit a portal user, navigate to the portal user list and click the three dots (…). This will show the Edit icon. Clicking the icon will redirect to the portal user edit page. [15]

Admin can update all the details and after updating the details click on the “Save” button. [16]

Unlock Contact:

If the admin has configured a security layer for portal users, including password complexity and lockout settings, users may get locked out after exceeding the allowed number of incorrect password attempts. In such cases, the admin can manually unlock the user account. This feature enables admins to restore early access to the portal for locked-out users, ensuring smooth operation without waiting for the lockout period to expire.

To unlock a user:

– Navigate to the portal user list and click on the three dots(…). 

– By Clicking on dots the admin can see the Unlock Icon, and clicking on that they can unlock the user.[17]

Delete Contact:

To Delete a portal user, navigate to the portal user list and click the three dots (…). By clicking on the dots the admin can see the Delete icon and by clicking on that they can see one warning (pop-up) message.  [17]

Click on the “Ok” button and the role will be permanently deleted from the portal. [18]

Admin can create and configure multiple sites for the current portal instance, but only one site can be published at a time. The admin can create, publish, and edit sites for that admin need to navigate to Settings > User Setting >  Portal User Roles. [1]

When Admin users log in to the Portal-Admin and authenticate the CRM, they will see the default published site. Admin can edit a default site or create a new site. [2]

To create a new site follow the below steps:

Click on the “Create button” on the right side of the corner. [3]

In a general setting, the admin can add basic site details like Name, logo and select time format. [1]

– Name: The name of adminportal or system (e.g., CRMjetty).

– Portal Enabled Language: The language in which the portal will be available (e.g., English).

– Default Language: The default language used when no other language preference is set.

– Portal Home Page: The main or landing page of the portal.

– Portal Name: The name of the portal (e.g., Hospital).

– Portal Logo: Upload a logo image for branding, displayed on the portal.

– Portal Favicon: Upload a favicon image that appears in the browser tab.

– Date Format: The format in which dates will be displayed (e.g., MM/DD/YYYY).

– Time Format: The format in which times will be displayed (e.g., 24-hour or 12-hour).

– Site Under Maintenance: Enable this option to display a maintenance message while the site is being updated or repaired.

reCAPTCHA helps protect portal pages, forms, and widgets from spam. Admin can configure either reCAPTCHA V2 or V3 to enhance security.

General Settings:

Enable reCAPTCHA:

– Check the Enable reCAPTCHA checkbox.

– Choose between reCAPTCHA V2 or V3 based on admin needs.

reCAPTCHA V2:

Requirements:

– Site Key: Used to render the reCAPTCHA on the page.

– Front-View: Displays an “I’m not a robot” checkbox that users must click to validate.

Applied to:

   – Form widget

   – Login widget

   – Registration widget

   – Forgot Password widget

   – Subgrid Forms in the form builder

– Visible at the end of forms and widgets where reCAPTCHA V2 is enabled.

reCAPTCHA V3:

Requirements:

– Site Key: Used to render the reCAPTCHA on the page.

– Secret Key: Used for server-side validation.

– Front-View: Verifies user actions with a score and provides a token automatically.

Applied to:

   – Page

   – Form widget

   – Login widget

   – Registration widget

   – Forgot Password widget

   – List widget

   – Recent Activity widget

   – Case Deflection widget

   – Chart widget

   – Counter widget

   – Knowledge Base widget

   – Search widget

   – Subgrid Forms in the form builder

Insert and configure the reCAPTCHA keys. Click on the Save button.

Note: Choose the version that best fits admin security needs and apply it to the relevant widgets and pages within the admin portal.

Admin can customize the site theme according to their requirements.

1. Font Customization:

– Base Font Family: Specify the font family for general text.

– Heading Font Family: Specify the font family for headings. [1]

2. Color Customization: 

– Theme Background Color: Sets the overall background color of the theme.

– Foreground Color: Sets the color used for text and other foreground elements.

– Primary Color: Used for primary buttons, links, and accents.

– Base Font Color: Sets the color for general text content.

– Heading Font Color: Sets the color for headings. [1]

3. Menu Customization:

– Menu Background Color: Sets the background color for the menu.

– Menu Text Color: Sets the color of the text in the menu.

– Menu Hover Color: Changes the color of the menu item when hovered over.

– Menu Font Size: Adjusts the font size for menu items. (Range: 14 to 30)

– Menu Font Weight: Sets the font weight for menu items (e.g., normal, bold).

– Menu Alignment: Aligns the menu items (e.g., left, center, right). [2]

4. Submenu Customization:

– Submenu Background Color: Sets the background color for the submenus.

– Submenu Text Color: Sets the color of the text in the submenu.

-Submenu Hover Color: Changes the color of the submenu item when hovered over.

– Submenu Font Size: Adjust the font size for submenu items. (Range: 14 to 30)

– Submenu Font Weight: Sets the font weight for submenu items (e.g., normal, bold). [2]

Admin can also set the default CRMJetty portal setting. By clicking on the “Rest to Default” button. [3]

Admin can add admin customized CSS for the portal and then apply the styles to various page sections and weights as needed.  [1]

Note: Adjust the class names and CSS properties according to admin-design preferences to customize different sections and weights.

Admin can manage and display the external login accounts set up through integrations. admin can only see those accounts in the dropdown that admin has configured in integrations.

1. Google

Select adminGoogle account to enable Google-based authentication.

2. Facebook

Configure and connect adminFacebook account for login integration.

3. Microsoft Identity

Link admin Microsoft account for authentication purposes.

4. LinkedIn

Setup and connect adminLinkedIn account for login integration.

Admin can select and manage these external accounts to provide users with various login options through the admin portal.

The admin can enhance the security for the portal by configuring various login methods.

1. Password Lock: Temporarily locks portal access after a set number of incorrect password attempts.

Configuration:

– No. of Wrong Attempts: Define the maximum number of failed login attempts before locking the user.

– Set Password Lock Timer: Specify the duration of the lockout period.

2. Two-Factor Authentication (2FA): Adds an extra security layer by requiring users to verify an OTP sent to their registered email upon login.

Configuration:

– OTP Active Duration: Set the time period for which the OTP is valid.

– No. of Wrong OTP Attempts: Define how many times users can enter incorrect OTPs.

– Set OTP Timer: Set the countdown timer displayed with the OTP in the user’s email.

– Disable Resend OTP: Specify the time period during which users cannot request a new OTP.

3. Verify Email: Sends an email verification link to new portal users to confirm their registration. [3]

– Social Media Logins: Users logging in with social media accounts (Google, Facebook, Microsoft) will receive an email verification link after successful authentication.

4. User Approval: Requires admin approval for new portal users.

– Social Media Logins: Users authenticated via social media also need admin approval.

5. Custom Password Complexity: Enforces password complexity rules to enhance security.

Configuration:

– Password Range: Set the minimum and maximum length of passwords.

– Character Requirements: Define required character types (uppercase, lowercase, digits, special characters).

– Reset To Default: Reverts the password complexity settings to default values.

Example Password Requirements:

  – Length: 8 to 16 characters.

  – Uppercase Letter: At least one.

  – Lowercase Letter: At least one.

  – Digit: At least one.

  – Special Character: At least one from the set (!, @, #, $, %, ^, &, *, (, )).

6. Password Expiration: Requires users to change their passwords regularly.

– Password Expiration Settings: Below options include

   – Never Expire, 

   – 1 Day

   – 2 Day

   – 1 Month,

   – 3 Months, 

   – 6 Months,

   – 1 Year.

Portal Front Side

– When a new contact is created, the “PasswordUpdateDate” value is initially set to null for all contacts.

– If the “Never Expire” option is selected, there is no need to check the following checkpoints related to password expiration, it’s providing a user a straight forward and continuous access approach without additional checks.

1.  When “Never Expire” is selected, the following checkpoints need not be checked:

 i) When any user registers using the Register Widget.

 ii) When a portal user logs in from the Login Widget.

 iii) When a portal user sets a password.

 iv) When a portal user initiates the Forgot Password

 v) When a portal user updates their password from the Profile Widget.

 vi) The same applies to User Account

2. When “Never Expire” is not selected, the following procedures are applied:

 i) During registration using the Register Widget, the PasswordUpdateDate is filled with today’s date (UTC).

 ii) When a portal user logs in from the Login Widget:

Case 1: If PasswordUpdateDate is null, set PasswordUpdateDate = Current DateTime (UTC) in encrypted format for both Contact and CRM User Detail upon successful login.

Case 2: If PasswordUpdateDate is not null, decrypt and compare with the “Password Expiry Duration.”

– If satisfied, redirect to the Dashboard.

– If not satisfied, redirect to the Set Password screen. After a successful password update, also update PasswordUpdateDate = Current DateTime (UTC) as an encrypted format at Contact.

Case 3:  The same flow applies for the Forgot Password procedure.

Case 4: In the Profile Widget:

– After updating the password successfully, update PasswordUpdateDate = Current DateTime (UTC) as encrypted format at the Contact.

Note: The new password must not be the same as the old password, which is enforced during the Set Password procedure.

Admin will only see the payment accounts in the dropdown that admin has configured in integrations.

Admin needs to select the payment account and click on the “Save” button.

The CRMJetty allows the Admin  to  add rules and set conditions to display specific object data in the front portal or control portal users’ access to certain object data.

To create a workflow admin needs to navigate to Settings > Portal Setting >  Workflow Management. [1]

Viewing Workflows

By clicking on “Workflow Management”, the admin will be navigated to the listing page, where the admin can view, search, and filter workflows by Action Type, object, Owner, and Date. [2]

Creating a Workflow:

To create a new workflow, click on the “+ Create” button, which will redirect the admin to the Create Workflow page.  On this page, the admin needs to configure the following details:

– Title: Enter a name for the workflow for easy identification.

– Roles: Choose the roles that this workflow will apply to.

– object: Select the object which the conditions will apply.(eg. Case, Order)

– Action Type: The admin can choose the action type between Load Data and Update Assign Rights. [3]

Action Types:

1. Load Data: This action allows the Admin  to filter and display only specific object data in the customer portal.

– Data will be sorted and displayed in various formats (e.g., List view, Data card, Recent Activity, etc.) based on the rules admin set.

– Select the fields, operators, and values to determine the data that portal users can view. [4]

2. Update Assigned Rights:  This action type is used to  manage portal users access rights (Edit, View, Delete) based on conditions. [5]

– For example: The Admin can restrict delete rights for certain records by setting specific conditions. 

Setting Workflow Conditions:

– After selecting an action type, the admin can set conditions based on the specific fields.

– Admin  can add multiple conditions and group them as needed. Using the AND/OR options, the admin can ensure that portal users see data or have access rights only when specific conditions are met. [6]

– For example, if the admin set a condition to show only “In Progress” and “On Hold” cases, portal users will view only  those specific records. [7]

Managing Rules with Group Options

Select Group

The Select Group option allows Admin  to group multiple conditions together. This feature is useful when Admin  want to combine conditions using either the AND or OR logic, controlling how access rights or data visibility is managed for portal users. [8]

Ungroup

The Ungroup option enables Admin  to separate previously grouped conditions. If the Admin no longer needs certain conditions to be treated as a unit, they can use this option to break them apart, allowing individual conditions to be managed independently. [8]

Change to OR

When using the AND logic by default, selecting Change to OR modifies the conditions to be evaluated with an OR relationship instead. This means that if any of the conditions are true, the action (like granting access) will be executed. [8]

Delete

The Delete option allows the Admin to remove any existing condition or group of conditions. This is useful when certain conditions are no longer relevant or need to be changed entirely. [8]

Add Clause

The Add Clause feature provides Admin  with the ability to insert a new condition into an existing rule set. This ensures flexibility by allowing new criteria to be added without disrupting the existing rules structure. [8]

Enabling Workflows

To apply a workflow to a page, navigate to Design > Page, open the page in Edit mode, configure the widget, and enable the workflow.

Admin  can apply workflows to various widgets like Case Deflection, Chart, Counter, Data Card, etc.

Admin  can assign workflows to a page by navigating to Design > Page. First, the admin should configure the appropriate widget on the page and ensure that the workflow is enabled.

Workflows can be applied to various widgets, including Case Deflection, Charts, Counters, Data Cards, and more.

Workflows in Forms and List Builders

Workflows can also be assigned at the field level in forms and list builders, particularly for lookup-type fields. Ensure that the lookup field is  related to an object  with an active workflow.

Widget Classification

Widgets may support either “Load Data Workflow” or both “Load Data” and “Update Assigned Rights” workflows:

Load Data Only: Supported by Charts, Counters, Knowledge Base, and Case Deflection widgets.

Both Workflows: Supported by Lists, Data Cards, Recent Activity, and Forms  widgets.

Step-by-Step Workflow Example

Scenario: Configuring a Workflow for High-Priority Cases

The Admin  need to configure a workflow that displays only “High Priority” cases on the case details page, ensuring that only  these cases are visible to the support team and they cannot be deleted.

1. Create a New Workflow

– Title: “High Priority Case”

– Roles: Assign the workflow to the “Support Team” role.

– object : Select “Case” as the object.

2. Action Types

Load Data:

– Condition: Select the “Priority” field, set the operator to “Equals,” and choose “High” and “Urgent” as the values. This ensures that only “High Priority” and “Urgent” cases are visible to portal users.

Update Assigned Rights:

– Condition:  Set the “Priority” field to “High” and “Urgent.”

– Action: Disable the “Delete” option. This prevents portal users from deleting cases marked as “High Priority” or “Urgent.”

3. Assign the Workflow

To implement the workflow, navigate to Design > Page, edit the relevant page, and enable the workflow in the widget settings.

After configuring this workflow, assign it to the case details page. Once assigned, only “High Priority” cases will be visible to the support team, and the option to delete these cases will be disabled.

Admin  can enable or disable an object in the portal, use  the object Configuration feature. object configuration is necessary when the admin adds a new object to the CRM.  To enable the object for the portal, select specific CRM objects  and drag and drop them into the Portal object section.

Note: Before configuring the object, Admin  must first sync the CRM with the portal.

Enabling or Disabling an object

To sync an object, navigate to Settings > User Settings > Object Configurations. [1]

In this section, Admin  can drag and drop “CRM objects ” into the “Portal objects ” section to sync them between the CRM and the portal.

Admin  can either  search for a CRM object by name or manually drag and drop it into the portal object section.

Once the configuration is complete, click the “Save” button to add the CRM object to the portal.

Note: If an object does not appear in the CRM object list, Admin  should first synchronize the CRM with the portal. Once the synchronization is complete, the object will be visible in the CRM object list.

If an admin wants to remove an object from the portal, they can simply drag and drop the portal object into the CRM object list. This action will remove access to that specific data through the portal.

Note: If an admin removes an object from the portal, it will no longer be accessible through the portal. Additionally, this specific object cannot be used in lists, forms, pages, etc.  However, certain objects  like cases or content cannot be removed, as they are primary objects  required to manage the portal.

Admin  can manage and customize the languages used in the portal to ensure it meets users preferences. To set up languages for the customer portal, follow these steps:

1. Navigate to Language Configuration:

Go to Settings > Portal Settings > Language Configuration. [1]

2. Enable Multi-language Support:

On this page, Admin  can enable multi-language support for the portal. CRMJetty Portal provides support for 41 languages. [2]

Note: In CRM language only shows the language which is enabled into the CRM system.

The list of available languages includes:

– English

– Arabic

– Basque

– Bulgarian

– Catalan

– Chinese (Hong Kong S.A.R)

– Croatian

– Czech

– Danish

– Dutch – Netherlands

– Estonian

– Finnish

– French – France

– Galician

– German

– Greek

– Hebrew

– Hindi

– Hungarian

– Indonesian

– Italian – Italy

– Japanese

– Kazakh

– Korean

– Latvian

– Lithuanian

– Malay – Malaysia

– Norwegian (Bokmål)

– Polish

– Portuguese – Brazil

– Romanian

– Russian

– Serbian (Cyrillic)

– Slovak

– Slovenian

– Spanish – Spain (Modern Sort)

– Swedish

– Thai

– Turkish

– Ukrainian

– Vietnamese

Admin  can enable any of these languages in the portal by dragging and dropping the respective language from the CRM Languages section to the CRMJetty portal Languages section. [3]

3. Save Configurations: 

After making the necessary changes, click on the Save button. [4]

Note: English is the default language and cannot be disabled.

Multi Language

Navigating to Multi Language, admin will be able to configure the labels for multiple languages. [5]

The first step is to Select Language for the respective labels. [6]

Further, choose Portal or CRM from the dropdown menu of Select Language Label. 

Portal: Select this option in order to change the label in the portal.  [7.2]

– Once admin select this option then admin will get the list of the default text of the message which is currently displaying in the portal. [8]

 – On the right side admin will get the value tab. admin can insert the translated value of the default text on the left side. [9]

CRM: If admin select this option then admin can change the language for all the text labels present in that CRM. [10]

– For example: we have selected Case CRM.

Now all the default text in the case CRM will be loaded below. 

Admin can insert the translated value for the default text on the left side. 

After configuring the language, click on the ”Save” button. Now multiple languages are enabled in admin portal. [11]

Import Text labels:

 Admin  can also import translated text labels:

1. Export Template 

– First, the admin needs to click on the Export Template button. The template file will be downloaded into the admin system. [12]

2. Add Translations:

– The template file will have information like Text Key, Default Text, and Language Specific Text. admin has to add the translated text in the Language Specific Text column.  [13]

3. Import the file:

– After adding the details in the sample file, Import the file. The value will be populated with translated labels. Now, the admin has to “Save” the settings to make it work properly.  [14]

Auto Translate:

– Admin can also auto-translate the labels rather than translating each label manually. There is one button on the top right corner of the language setting named Add Google Translate key. [15]

– Once the button is clicked, insert the Google Translation key. [16]

– Click on the “Save” button and adminKey will be saved successfully. 

Note: The admin must enable the “Translate API” from Google developer console for the website domain (portal domain).

Once admin have inserted the Translate API key, admin are able to Auto Translate the Portal labels by selecting the language(s).

Now, click on the ‘Auto Translate’ button, to translate all the labels at once based on the language selection.  [17]

Now, Save the labels to make it work on the portal. 

Admin can as well remove all the labels at once by clicking on the “Clear All” button and then, Admin can see all the fields would be cleared.  [19]

CRMJetty allows Admin  to design and configure the listing view for various objects. Admin  can create, edit, preview, and publish lists that will be used in page builders. The dynamic layout of the list view can be designed using CRM fields.

The List Builder enables Admin  to create, duplicate, delete, filter, preview, and translate list views. To access these features, Admin  need to navigate to Design > Lists. [1]

On the listing page, Admin  can view the following columns: Title, Status, Language, Owner, object, and Created On dates.

The Admin can apply filters based on Title, Status, and object. Additionally, the Admin can use Advanced Filters to further refine the list data.

Admin  can create a listing page for any object. By clicking on the + Create button, a popup will appear where the admin needs to insert the ‘Title’ of the list page.

Click on the “Save” button to design the listing page layout. This will redirect the admin to the List layout design page.

From the right side, Admin  can either create a new list view or use an existing ready list from the CRM.

Create New: The admin can choose the “Create New” option to build a list from scratch.

Use Existing: The admin can select the “Use Existing” option to utilize a list that has been already created in CRM. [2]

Admin needs to select the object for which the list view layout needs to be created. [3]

After selecting the “Object”, Admin  will see a list of fields enabled from CRM. The required fields can be drag and drop from the right to the left to add columns to the list.

There will be search functionality available for the admin to search for a field. [1]

By clicking on the Settings icon, the Field Name and Data Type of the field will be displayed. The admin can also edit the field details. [2]

After configuring the list, Admin  can either save it as a “Draft” or “Publish” it. 

Draft: For internal use, editing, and review. Not visible to portal users. [3]

Publish: Final version; once published successfully, it can be used by Admin  while configuring the list widget in the page builder. [4]

Note: Admin  cannot use draft lists while configuring the page; the list must be published to be used in the page builder while configuring the “list widget”.

Admin  have the option to select a pre-configured ‘List view’ layout from CRMJetty. By selecting the “Use Existing” option, all available ready-made list layouts (CRM object views) will be accessible. [1]

Steps to Configure the List View:

From the View dropdown, select a ‘List view’. The fields associated with that specific list view, as configured in CRM, will be displayed. [2]

When the Admin selects a view, the list fields are automatically added to the fields in the right-side panel. [3]

Note: The fields are added based on the CRM list, and the Admin can modify the list as needed.

Field Customization:

The admin needs to click on the “Settings” icon to update or change the labels of any field. While editing a field, the data type will be shown. [4] 

To remove a field, the admin needs to click on the ‘delete’ icon. [5]

If the admin wants to display a field as an image, the admin can use the “Show as Image” option in the Field Configuration that allows the string value to be shown as an image. 

Note: To ensure a proper view in the portal, the admin should add the correct image path. 

Otherwise, a dummy image will be displayed. The admin needs to click on the “Settings icon” to open the field configurations and check mark the “Show as Image” option. [1]

Note: If the “Show As Image” checkbox is checked, the “Enable for Filter” checkbox will be disabled, as filtering is not applicable to image-type data.

After updating the Field Setting, the admin needs to click on the Save button. [2]

To finalize the list builder by clicking on the Publish button. The admin can also save it as a draft by clicking on the Save As Draft button.[3]

 The admin can also save it as a draft by clicking on the Save As Draft button.

Admin can Enable the filter option to allow portal users to filter listing records on the front portal side.

By checking the “Enable for Filter” checkbox, portal users will have a searchable option for the CRM Fields. [1]

Admin can enable filter globally by checking on the “Lookup Global Access” checkbox. [2]

When the Admin enables the Filter option for a form field, the “Form Global Access” checkbox becomes visible in the configuration settings.

Enabling Lookup Global Access ensures the data displayed in the lookup field is global, representing all data for the associated object.[1]

Example:

If Customer Lookup Global Access is enabled, the lookup will display all customer data, regardless of any specific filters or restrictions.

This feature provides flexibility to access a comprehensive dataset for the selected object.

If the field’s data type is a lookup and the “Enable for Filter” checkbox is checked, the Workflow Setting will become visible.

By clicking ‘Workflow Setting’, the “Data Load” dropdown will appear, showing the workflows (with Data Load action type and target object of the field) created in the Workflow Management. [2]

Note: Admin will only view the specific lookup workflows

Admin can select the workflow according to the requirement.

Admin can also add a new workflow by clicking on the “+” icon. [3]

By clicking on the icon admin will redirect to the lookup page and view the object by default selected admin just need to enter other details. [4]

After selecting the workflow, click on the Save button. [5]

The Custom Lookup View allows you to customize how lookup fields display data in the List Builder.

Steps to Configure

1. Enable the Feature

  – Go to the Field Configuration Settings for the lookup field.

  – Enable Custom Lookup View  [1]

2. Select Fields

– In the Custom Lookup Settings, the Admin can view all the lookup objectsenabled from the CRM for the specific field. This allows the Admin to select and configure targeted objectsfor the lookup, ensuring personalized and relevant data display in the List Builder.

– For example, if the Account Object is enabled, the dropdown will display: [2]

– Account Name (primary field, fixed at the top). [2]

– Account Rating (additional field). [2]

Note: The Account Name field is mandatory and is automatically selected as the primary field. Its position is fixed at the top of the field list.

3. Set Sequence

– The Admin can configure these fields and their sequence for a customized lookup view. [3]

– Arrange the fields in the desired order.

– Example sequence:

  1. Account Name

  2. Account Rating

– After all the configuration, click on the “Save” button to apply changes to the front-end view.

Note:

– Field Limit: Maximum of 5 fields (1 primary + 4 additional).

– Language Support: Names appear in configured languages or default to English.

– This setup streamlines lookups, displaying only relevant fields in your preferred order

Admin  can create or update the layout of the list view using the JavaScript Code Editor if custom JS code is available.

By clicking on the JS Editor, an editor will pop up where the admin can add or paste the JS code. [1]

Once edited or pasted, click the “Apply” button and publish the List Builder record.

The admin can enable the “Payment Configuration” option to facilitate the integration of payment processing within the list views. This allows the portal users to interact with payment-related fields directly from the list view, making it easier to manage transactions, view payment statuses, and perform payment actions without navigating away from the current page.

Steps to Configure Payment Options:

Enable Payment Configuration:

 – To activate this feature, the admin must check the “Enable Payment” toggle is active.

– Note: This feature can only be enabled if the object includes an Amount (Currency) type field.

Button Label:

The admin should enter the text label to be displayed as an option in the record’s context menu. [1]

Select Amount Field:

The admin should choose the object field to be used as the amount field for processing payments. [1]

Set Conditional Field to Enable Pay Button:

The admin must select the object field that determines when the Pay button will be displayed. [1]

Set Conditional Field Value to Enable Pay Button:

The admin should choose the conditional value field that triggers the display of the “Pay” button. Multiple values can be selected as needed. [1]

Transaction Log Settings:

– The admin should configure the Transaction Log Settings to synchronize transaction data with the CRM.

– Select Transaction object: The admin must choose the transaction object and record transaction details. [2]

– Select Description Field: The admin should choose the object field for a short description. [2]

– Select Payment object: The admin should select the field in the transaction object use as the payment object field. [2]

– Select Payment Record: The admin needs to choose the field in the transaction object use as the payment record field. [2]

– Select Payment Method: The admin must select the field in the transaction object use as the payment method field. [3]

– Set Amount Field: The admin should choose the field in the transaction object for the payment amount. [3]

– Select Payment Transaction Log: The admin needs to choose the field in the transaction object for the Payment Transaction Log. [3]

– Select Payment Status: The admin should select the field in the transaction object for the Payment Status. [3]

After configuring the payment method, the admin should “Update” the changes and publish the list. 

CRMJetty provides Admin  to configure a list field as a rating field. To initiate this setup, Admin  must first activate the “Enable Rating” option. This function allows Admin  to designate a specific field to display ratings.

Supported Data Types for Rating Field:

  – Integer

  – BigInt

  – Decimal

  – Double

In the rating field configuration, Admin  can choose icons from the icon picker, with available options including thumbs and stars. Furthermore, Admin  can select various colors using the color picker. [1]

Note: If a field is used in the Datacard widget, it cannot be deleted or have its rating functionality disabled via the List Builder. In the list view, portal users will only see the rating fields. They cannot modify the rating configuration, the icons and colors are only set by the admin from the backend.

From the listing page of the ‘List’ builder records, all available languages will appear in the Language column.

Translated languages will be shown in dark-coloured buttons, while untranslated languages will appear in light-coloured buttons.

The admin can translate the list record in two ways, one is by clicking on the light-coloured button and second is by selecting the specific record and clicking the ‘Translate’ icon from the record options. 

Once the admin clicks on the list builder record it will automatically translate to the selected language.

Admin  can also translate the list layout records from the edit list. At the top, the admin can see the“Languages” option and enabled languages will be displayed.

Select the language and click on the “Update” button, it will take a few seconds to translate all the CRM content, such as text labels and messages.

Once the list layout record is translated in a listing page you can view the language in highlighted color, that will ensure that the language is translated successfully.

Multiple List Translation

1. Translating Lists in Bulk:

The admin can translate multiple list layout records simultaneously by selecting multiple lists. [1]

2. Language Selection:

If multiple languages are enabled, a dropdown menu will appear, allowing the admin to select one language for translation. [2]

3. Translation Report:

After translating the selected lists, a pop-up will appear on the screen, displaying the translation status of the records/list.

Note: Ensure that all fields are translated in Settings > Portal Settings > Language Settings to guarantee proper translation of the fields.

To preview the list, Admin  need to either save the list as a draft or publish it. In both scenarios, Admin  can preview the list to see how it will appear on the front end.

Note: In preview mode, Admin  cannot click on any fields, the preview only displays the layout of the list. [2]

To edit a list, navigate to the portal lists and click the three dots (…). This will show the Edit icon. Clicking the icon will redirect to the edit list page. [1]

Admin can update all the details and configurations, after updating the details click on the “Update” button. [2]

To Delete a portal list, navigate to the portal list and click the three dots (…). [1]

By clicking on the dots the admin can see the Delete icon and by clicking on that they can see one warning (pop-up) message. Click on the “Ok” button and the role will be permanently deleted from the portal. [2]

Bulk Delete lists:

To delete a multiple list at once follow the below steps:

List Selection:

The admin should start by selecting the lists for deletion. This can be done by clicking on the checkboxes beside each list. [3]

Choosing Bulk Action:

After selecting the lists, the admin needs to proceed to click on the bulk action checkbox. From the available options, select the “Delete” option. [4]

Confirmation Process:

A confirmation pop-up will appear after selecting the “Delete” option. To finalize and permanently remove the selected lists, the admin must click the “OK” button. If the deletion is not required then the admin can simply click the “Cancel” button to exit the process. [5]

1. Publishing a List:

– To publish a portal list, navigate to the list and click the three dots (…). Clicking on the dots will reveal the “Publish” Icon. [1]

– By clicking on the icon the list will be published and the admin can view the success message on the right side of the page. [2]

Bulk Publish Lists

1. List Selection:

– The admin should start by selecting the lists to be published. This can be done by clicking on the checkboxes beside each list object. [3]

2. Choosing Bulk Action:

– After selecting the lists, the admin needs to click on the bulk action checkbox. From the available options, select the “Publish” option. [4]

By clicking on the publish option the selected list will be published and the admin can view the success message on the right side of the page. [5]

1. Duplicating a List:

To duplicate a portal list, navigate to the list and click the three dots (…). Clicking on the dots will reveal the “Duplicate” icon. Selecting this button will initiate the duplication process. [1]

2. Confirmation Process:

– Once the “Duplicate” button is clicked, the list will be copied, and a new duplicate list will appear in the portal.

– By clicking on the duplicate icon the selected list will be duplicated, and added a list as “List name – Copy”.  [2]

– After duplication the admin can view the success message on the right side of the page. [2]

Bulk Duplicate Lists

1. List Selection:

The admin should start by selecting the lists to be duplicated. This can be done by clicking on the checkboxes beside each list object. [3]

2. Choosing Bulk Action:

After selecting the lists, the admin needs to click on the bulk action checkbox. From the available options, select the “Duplicate” option.

By clicking on the duplicate icon the selected list will be duplicated, and added in a list as a “List name – Copy”. (eg. Orders-Copy)[4]

After duplication the admin can view the success message on the right side of the page. [4]

To preview a portal list, navigate to the list and click the three dots (…). Clicking on the dots will reveal the “Preview” icon. Selecting this button will open a preview window displaying the layout of the list. [1]

Note: The admin cannot add or modify any content within the list during this preview, it is just a list layout. [2]

Admin  can create a form for any object. By clicking on the “+ Create” button, a popup will appear where the admin needs to insert the ‘Title’ of the form.

Click on the “Save” button to design the form page layout. This will redirect admin to the Form layout design page. [1]

The Admin can create the portal user form for the customer portal. To create the form, the first admin needs to create a form layout for that admin can follow: Add Section > Add Grid > Add Fields.

Add Section: On the left side of the page, the admin can view the sections and by clicking on the “+” icon the admin can add a new section. Admin  can edit the panel and update the “Panel Title”. After editing, click the Save button. as shown in the mentioned screenshot. [2]

Add Grid: After adding the section the admin needs to select the grid, for that, the admin needs to click on the “Add Grid” button as shown in the mentioned screenshot. [3]

By clicking on the button, the admin can view the different grid options, when selecting the grid it will directly add to the selected section as shown in the below screenshot. [4]

Add fields: After adding the grid the admin adds fields to the grid, This can be done in two ways:

1. Create New: The admin can choose the Create New option to build a form from scratch.

2. Use Existing: The admin can select the Use Existing option to utilize a form that has already been created in CRM. [5]

Note: The grid supports only one field per box. Admin should ensure the sections are designed accordingly.

After designing a layout, the admin first needs to select the object from the drop-down list. [1]

Note: The admin can only see objects  that are synced with the portal. If the admin cannot find the object in the list, they must first sync the “CRM object” to the “Portal object.”

– Once the object is selected, the admin can design the layout for the Add, Edit, and Detail pages of the new Form. 

– There are two Copy options available: “Copy to Edit” and “Copy to Detail”. The admin can copy the ‘Add’ form design to both the ‘Edit’ form and the ‘Detail’ form. [3]

Note: If the admin is creating a Detail type form, the options “Copy to Add” and “Copy to Edit” will not be available.

– After selecting the object, the admin will see a list of fields enabled from CRM. The required fields can be dragged and dropped from the right side to the left side of the grid layout. [4]

– A search functionality is available for the admin to find specific fields.

To configure the fields, the admin can perform the following actions:

– Field Settings: By clicking on the Settings icon, the admin can configure following settings 

– Label: Define the field’s name visible to the portal user.

– Placeholder: Insert text that appears inside the field before data entry.

 – Help Tip: Provide additional guidance or information about the field.

– Default Value: Set an initial value that populates the field by default. [5]

Attributes Configuration: The admin can also set the field attributes such as ReadOnly and Required:

– Read Only: When this checkbox is enabled, portal users will not be able to enter data in the field.

– Required: Enabling this option makes the field mandatory, ensuring that portal users must fill it out before proceeding. [6]

When the Admin enables the Filter option for a form field, the “Form Global Access” checkbox becomes visible in the configuration settings.

Enabling Form Global Access ensures the data displayed in the form field is global, representing all data for the associated Object. [1]

Example:

If Customer Form Global Access is enabled, the form field will display all customer data, regardless of any specific filters or restrictions.

This feature provides flexibility to access a comprehensive dataset for the selected Object.

The Custom Form View allows you to customize how form fields display data in the Form Builder.

Steps to Configure

1. Enable the Feature

– Go to the Field Configuration Settings for the form field.

– Enable Custom Form View. [1]

2. Select Fields

– In the Custom Form Settings, the Admin can view all objectsenabled from the CRM for the specific field. This allows the Admin to select and configure targeted objectsfor the form field, ensuring personalized and relevant data display in the Form Builder.

– Example:

If the Account Object is enabled, the dropdown will display: [2]

  – Account Name (primary field, fixed at the top). [2]

  – Account Rating (additional field). [2]

Note:

– The Account Name field is mandatory and is automatically selected as the primary field. Its position is fixed at the top of the field list.

3. Set Sequence

– The Admin can configure these fields and their sequence for a customized form view. [3]

– Arrange the fields in the desired order.

– Example sequence:

  1. Account Name

  2. Account Rating

After completing the configuration, click on the “Save” button to apply changes to the front-end view.

Notes:

– Field Limit: Maximum of 5 fields (1 primary + 4 additional).

– Language Support: Field names appear in configured languages or default to English.

– This setup simplifies form configurations, displaying only relevant fields in your preferred order.

The admin can access ready-made ‘Form’ layouts that are configured from the CRM. By selecting the Use Existing option, the admin will see all the available Form layouts (CRM object views) and will have the ability to edit the fields as needed. [1]

Once the admin selects any ‘Form view’ from the Existing Forms drop-down, the fields of that specific form view, as configured in CRM, will be displayed. The admin can select existing CRM fields for the Add, Edit, or Detail page, depending on the form type. [2]

The admin can filter existing forms by selecting specific record types. If no record types are selected, all forms for the chosen object will be displayed.  [3]

The admin can add or remove fields as needed. Fields can be dragged and dropped from the list on the right side, and any field can be removed by clicking on the ‘delete’ icon.

When editing a field, the admin will have access to field-related options for display to portal users in the customer portal. [4]

Admin  can hide specific fields from the form by selecting the “Hidden” checkbox in the form builder. This hidden field will not be visible on the front-end form, but it will have a default value set through the field settings. [1]

For “Edit” type forms, this feature applies only if the field is empty or null; it will automatically set the default value without altering any previously entered data.

For Example:  the “Case Type” field might be hidden in the form, but it will still appear in the list view with the assigned default value.

A rating field allows portal users to provide a numerical rating or feedback for items like products, services, or content.

This functionality can be applied to specific data types like Integer, BigInt, Decimal, and Double.

The rating is visually represented through stars or thumb symbols. Admin  can configure the rating fields into various components such as Form (Add, Edit, and Detail views), List, and Data Card widgets.

Note: CRMJetty’s default configuration supports a maximum of 5-star ratings, and this setup is not adjustable by the admin.

Rating Fields Configuration

In the Form Builder, Admin  can configure the rating field by selecting the “Enable Rating” option within the field settings. [1]

– Icon Picker: Admin  can choose between different icons (e.g., thumbs, stars) for the rating field using the icon picker.

– Color Picker: Different colors can be selected for the icons, allowing customization of the rating field’s appearance.

– Compatibility: Rating fields can be configured for Add, Edit, and Detail form types. 

Note: If the Barcode input feature is enabled, admin cannot configure the rating feature. It can not used simultaneously on the same field.

– Read-Only Setting: Admin  can enable the “Read-Only” attribute to prevent portal users from modifying the rating field. This can be applied to both Add and Edit forms. [2]

Note: If this feature is enabled, the rating field will be disabled for front-end users, displaying only the default value or passing a null value if default is not set.

Front-End View for Rating Field:

On the front-end, portal users can interact with the rating field by assigning both whole and half-star ratings (e.g., 2, 4, 4.5, 1.5). [3]

The icon and color will appear as configured by the admin, providing a user-friendly visual representation of the rating.

Admin can enhance data entry efficiency by enabling barcode or QR input within relevant forms. This feature allows portal users to scan barcodes or QR codes, speeding up data collection and reducing manual input errors.

Form Builder Settings:

In the field settings within the Form Builder, Admin  can enable the “Barcode/QR Code Input” option. This setting is applicable to fields with data types such as String, Integer, Decimal, and BigInt.

The barcode/QR code input feature can be configured for Add, Edit, and Detail form types. [1]

Enable Input Text:

If this checkbox is enabled, portal users can enter data manually in addition to scanning barcodes or QR codes. If disabled, the field will be read-only, accepting input only through scanning. [1]

Note: If the rating input feature is enabled, admin cannot configure the Barcode/QR feature. It can not be used simultaneously on the same field. 

Front-End View for Barcode/QR:

When the barcode/QR code input is enabled, a camera icon will appear in the form field.

Portal users can click this icon to activate their device’s camera and scan barcodes or QR codes for efficient data input. [2]

Supported Barcode/QR Formats:

CRMJetty supports a variety of barcode and QR formats, including QR Code, AZTEC, CODE_39, CODE_93, CODE_128, ITF, EAN_13, EAN_8, PDF_417, UPC_A, UPC_E, DATA_MATRIX, MAXICODE, RSS_14, and RSS_EXPANDED.

This feature allows Admin  to customize the visibility and behavior of fields based on certain conditions.  

Default Field Visibility

– Visible: The field is displayed on the form by default.

– Hidden: The field is not displayed on the form by default. [1]

Hide Field Based on Conditions

Admin can hide the fields based on the different conditions:

– Conditional Field: Choose the field that will determine when the current field should be hidden.

– Multi-Select Matching Category: Select categories for fields with multiple options, which will control the condition for hiding.

– Conditional Field Option: Specify the value or option from the conditional field that will trigger the field to be hidden. [2]

For Example: Admin have a form with a field called “Discount Code” that admin wants to show only when a checkbox “Special Offer” is checked.

– Default Field Visibility: Set the “Discount Code” field to Hidden by default.

– Conditional Field: “Special Offer” (the checkbox).

– Multi-Select Matching Category: Not applicable here.

– Conditional Field Option: Checked (when the checkbox is selected).

By configuring this the “Discount Code” field will only appear when the user selects the “Special Offer” checkbox.

In a form builder if the If field’s data type is a lookup then Workflow Setting will become visible.  Admin can only configure workflow for Add and Edit forms. [1]

By clicking ‘Workflow Setting’, the “Data Load” dropdown will appear, showing the workflows (with Data Load action type and target object of the field) created in the Workflow Management.

Admin can select the workflow according to the requirement. [2]

Admin can also add a new workflow by clicking on the “+” icon. [3]

After selecting the workflow, click on the Save button.

Admin  can enhance the user experience in the customer portal by configuring a progress bar for specific dropdown fields in any object form. This feature is applicable to dropdown-type fields such as Picklist, State, and Status. [1]

1. Enable Progress Bar:

In the Field Configuration section, locate the “Show as Progress Bar” option and enable it to display the progress bar to portal users.

2. Configure Field Options:

Set the sequence of the available options for the selected dropdown field by dragging the options up or down to rearrange them.

3. Select Design Layout:

Choose from two design layouts to display the progress bar in the customer portal.

4. Field Attributes:

Configure the field as Required or Read-Only based on requirements.

Note: The progress bar status reflects the “Advanced Field Management” settings, which control the field options visible to portal users.

This configuration allows the admin to link data or records where one object (the parent) is associated with one or more other objects  (the children). [1]

Note: The Parent-Child Link feature is only enabled in the Add Form Type. [1]

On the add from configuration, the admin can view the parent-child link toggle button the admin needs to click on to activate the feature. After that admin needs to configure the following details: [1]

– Child object: Choose the object that will act as the child in the relationship.

– Relationship Type: Select the type of relationship that defines how the parent and child objects  will be connected.

– Create Unique Records On: Identify the field that will ensure each record is unique.

– Fields Display: The fields will be shown based on the selected relationship type.

Step-by-Step Example for Parent-Child Link:

Scenario: Suppose the admin configuring a Customer Order Management System

Then admin needs to configure the following fields:

– Child object: The admin needs to select “Order Items” as the child object, which will be linked to the “Customer Order” parent object.

– Relationship Type: The admin chooses “Order (Customerid)”, indicating that each customer order can have multiple order items.

– Create Unique Records On: The admin identifies the “Order ID” field to ensure each order record is unique.

– Fields Display: Based on the Order (Customerid) type, fields like “Item Name,” “Quantity,” and “Price” will be displayed for selection in the form.

The admin can enable the “Payment Configuration” option to integrate payment processing directly within the form. This setup allows portal users to interact with payment-related fields within the form itself, facilitating easier management of transactions, viewing payment statuses, and performing payment actions without needing to leave the form page.

Note: The payment configuration feature is enabled for the Add -Edit -Detail Form Type.

Steps to Configure Payment Options:

To enable payment functionality for a specific object’s form record, follow these steps: 

1. Enable Payment:

Enable the toggle button from the right side of the panel “Payment configuration” to activate payment options. [1]

2. Button Label:

Enter the text the admin wants to display as a title of the field.

3. Set Amount Field:

The admin should choose the field that represents the payment amount.

4. Set Conditional Field to Enable Pay Button:

The admin must select the conditional field that will control when the Pay button appears.

5. Set Conditional Field Value to Enable Pay Button:

The admin needs to select the conditional value that will trigger the Pay button. Multiple values can be chosen if needed.

6. Transaction Log Settings:

The admin should configure settings for syncing transaction data with the portal.

7. Select Transaction object:

The admin must choose the object where transaction details will be stored.

8. Select Description Field:

The admin should select the field to be used for a short description of the transaction.

9. Select Payment object:

The admin must pick the field from the transaction object that will serve as the payment object.

10. Select Payment Record:

The admin should choose the field in the transaction object to be used as the payment record.

11. Select Payment Method:

The admin needs to select the field that represents the payment method.

12. Set Amount Field:

The admin should identify the field where the payment amount will be recorded.

13. Select Payment Transaction Log:

The admin must choose the field that will act as the Payment Transaction Log.

14. Select Payment Status:

The admin needs to select the field that will display the Payment Status.

Once all configurations are complete, the admin should click the Save button at the end of the process. Finally, Publish the page to apply these changes in the customer portal.

The admin can create or update the layout of the form view using the JavaScript Code Editor if there is any custom JS code. [1]

By clicking on the Code Editor, an editor will pop up where the admin can edit or paste the JS code. Once the code is edited or pasted, the admin should click the Save button and publish the Form builder record. [2]

Additionally, the admin can edit or paste JavaScript code to modify the UI and appearance to match preferences or align with the portal’s theme.

From the listing page of the ‘Form’ builder records, all available languages will appear in the Language column.

Translated languages will be shown in dark-coloured buttons, while untranslated languages will appear in light-coloured buttons. [1]

Admin  can translate the Form record by clicking on the light-coloured button.  Once clicked, the Form builder record will automatically translate to the selected language. [1.1]

Admin  can also translate the form layout records from the edit form page. At the top, the “Languages” option and enabled languages will be displayed. 

Once the form layout record is translated from the listing page or the page layout edit page, it will take a few seconds to translate all the CRM content, such as text labels and messages. [2]

Multiple Form Translation

1. Translating Forms in Bulk:

Admin  can translate multiple form layout records simultaneously by selecting multiple forms. [3]

2. Language Selection:

If multiple languages are enabled, a dropdown menu will appear, allowing the admin to select one language for translation. [4]

3. Translation Report:

After translating the selected forms, a pop-up will appear on the screen, displaying the translation status of the records/forms. [5]

Note: Ensure that all fields are translated in Settings > Portal Settings > Language Settings to guarantee proper translation of the fields.

To preview the form, the admin needs to either save the form as a draft or publish it. In both scenarios, the admin can preview the form to see how it will appear on the front end. [1]

Note: In preview mode, the admin cannot click on any fields; the preview only displays the layout of the form.

To edit a form, navigate to the portal forms list and click the three dots (…). This will show the Edit icon. Clicking the icon will redirect the admin to the edit form page.

The admin can update all the details and configurations. After updating the details, click the Update button.

To delete a portal form, navigate to the portal form list and click the three dots (…). Clicking on the dots will reveal the Delete icon. Clicking on this will display a warning (pop-up) message.

Click the “Ok” button, and the form will be permanently deleted from the portal. [1]

Bulk Delete Forms

1. Form Selection:

The admin should start by selecting the forms for deletion. This can be done by clicking on the checkboxes beside each form. [2]

2. Choosing Bulk Action:

After selecting the forms, the admin needs to click on the bulk action checkbox. From the available options, select the “Delete” option. [3]

A confirmation pop-up will appear after selecting the “Delete” option. To finalize and permanently remove the selected forms, the admin must click the OK button. If deletion is not required, the admin can simply click the Cancel button to exit the process.

1. Drafting a Form:

To draft a portal form, navigate to the form list and click the three dots (…). Clicking on the dots will reveal the “Draft” icon. By clicking on this icon, the form will be saved as a draft, and the admin can view the success message on the right side of the page. [1]

Note: Draft forms are disabled for the customer portal. To use these forms, the admin must publish them.

2. Bulk Draft Forms:

The admin should start by selecting the forms to be drafted. This can be done by clicking on the checkboxes beside each form object.

After selecting the forms, the admin needs to click on the bulk action checkbox. From the available options, select the “Draft” option.

By clicking on the draft option, the selected forms will be saved as drafts, and the admin can view the success message on the right side of the page. [2]

1. Publishing a Form:

To publish a portal form, navigate to the form list and click the three dots (…). Clicking on the dots will reveal the “Publish” icon. By clicking on this icon, the form will be published, and the admin can view the success message on the right side of the page. [1]

2. Bulk Publish Forms:

The admin should start by selecting the forms to be published. This can be done by clicking on the checkboxes beside each form object.

After selecting the forms, the admin needs to click on the bulk action checkbox. From the available options, select the “Publish” option. [2]

By clicking on the publish option, the selected forms will be published, and the admin can view the success message on the right side of the page.

1. Duplicating a Form:

To duplicate a portal form, navigate to the form list and click the three dots (…). Clicking on the dots will reveal the “Duplicate” icon. Selecting this button will initiate the duplication process. [1]

Once the “Duplicate” button is clicked, the form will be copied, and a new duplicate form will appear in the portal. The duplicated form will be named “Form Name – Copy” (e.g., Add Orders-Copy). [2]

After duplication, the admin can view a success message on the right side of the page.

2. Bulk Duplicate Forms

The admin should start by selecting the forms to be duplicated. This can be done by clicking on the checkboxes beside each form object.

After selecting the forms, the admin needs to click on the bulk action checkbox. From the available options, select the “Duplicate” option. [3]

The selected forms will be duplicated and added as “Form Name – Copy” (e.g., Add Orders-Copy). After duplication, the admin can view a success message on the right side of the page. [4]

To preview a portal form, navigate to the formlist  and click the three dots (…). Clicking on the dots will reveal the “Preview” icon. Selecting this button will open a preview window displaying the layout of the form. [1]

Note: The admin cannot add or modify any content within the form during this preview; it is just a form layout.

Admin  can display the form content of any object in a step-by-step manner in the customer portal by enabling the “Multi-Step Form” option. This feature allows portal users to navigate through the form in sections, making it easier to manage complex forms.

1. Enable Multi-Step Form: In the Form configuration panel under “Web Forms,” check the “Enable Multi-Step Form” option.

2. Configure Navigation Buttons:

– Previous Button Label: Set the label for the button that allows users to navigate back to the previous section of the form.

– Next Button Label: Set the label for the button that allows users to move to the next section of the form. [1]

3. Section Configuration:

– The form will be divided into sections based on the configuration. Users will navigate through these sections step-by-step.

4. Edit Navigation Button Labels:

– In the Edit form settings, customize the labels for the Previous and Next buttons to better fit the needs.

Once you setup multi step form configuration “Update or Publish” the form.

Note: The Multi-Step Form feature is available for Add/Edit type forms and can be used with both “Create New” and “Use Existing” CRM layouts. Once configured, the form can be placed in the Page Builder, and its multi-step navigation can be previewed.

Admin  can use the Sub-Grid Widget to display forms in a sub-grid view. Admin simply drag and drop the Sub-Grid widget onto the designated grid area.  [1]

Sub-Grid Configuration

By clicking on the field Settings icon, the Sub-Grid Configuration panel will open up.

– Label: Enter the label for the sub-grid section.

– Select object: Choose the object for which the sub-grid section will be created.

– Select Relationship: Select the relationship (object) to associate with the chosen object form.

– Select List View: Pick the list view to display for the selected relationship type in the sub-grid. [2]

Managing Sub-Grid Access

Admin  can manage sub-grid access through Access Settings by enabling or disabling the options for creating, editing, and deleting records.

Allow Creating Records:

– Button Label: Insert the label to display for creating records on the portal.

– Select Form: Choose the form that will appear on the portal when creating records.

– Select Record Type: All active record types related to the selected object will be available here. [3]

Note: If there are no record types in CRM, the Select Record Type field will not be visible.

Allow Editing Records:

– Button Label: Insert the label to display for editing records on the portal.

– Select Form: Choose the form that will appear on the portal when editing records. [4]

Allow Detail Redirection:

– Button Label: Insert the label to display for viewing record details on the portal.

– Select Page: Choose the page to which users will be redirected when they click the “Detail” button. [5]

Allow Deleting Records:

– Button Label: Insert the label to display for deleting records on the portal.

– Submit Button Label: Insert the label for the submit button. [6]

Workflow and Access Configuration

– Enable Workflow: This option activates workflows for the sub-grid section.

– Data Loading Workflow: Includes workflows with data load actions and the selected object for the sub-grid.

– Update Assign Rights Workflow: Contains workflows with Update Assigned Rights actions and the selected object for the sub-grid. [7]

Enable Global Access: Enable this feature to allow portal users to access global data. If unchecked, portal users will only access their records within the sub-grid. [8]

Note: If global access is enabled, users will have a filter option to show either “My Records” or “All Records.” 

Enable reCAPTCHA: Activate reCAPTCHA for the sub-grid in the portal. [8]

Note: The sub-grid option is only available for edit and detail form types.

Example: In the Project form, users will see a “Project Tasks” section where they can view, add, edit, or delete tasks associated with the project. If Global Access is enabled, a filter option appears, allowing users to toggle between “My Tasks” and “All Tasks”. This configuration ensures that users can manage related tasks directly within the context of the project they’re working on, making it easier to keep track of project progress.

Front-side view subgrid:

The Subgrid Form View provides a streamlined, interactive interface, displaying associated records or related objectsin a table format within the main Object form. This subgrid view enables users to quickly access, review, and manage linked data without navigating away from the main form.

Admin  can use the Note Widget to display notes and attachments in a form view. Simply drag and drop the Note & Attachment widget onto the designated grid area. [1]

Configuration Settings:

– Label: Admin insert the label for the section (e.g., “Notes”).

– Allow Creating Records:  Admin enable this option to allow portal users to create records.

– Button Label:  Admin insert the label for the create button (e.g., “Create”).

– Allow Deleting Records:  Admin enable this option to allow portal users to delete records. [2]

– Default Accordion Behavior: Admin select between Expanded or Collapsed view.

– Enable Global Access:  Admin allows portal users to access global data or restrict them to their records.

– Select Design Layout: Admin select the layout between “Chat Style” or “Grid Style”.

The Design Layout option determines how notes and attachments are shown on the portal:

1. Chat Style:

Look: Notes and attachments appear like chat messages.

Example: Imagine a support portal where users can leave comments or notes about an issue. Using the Chat Style, each note would appear as a message, making it easy to follow the discussion. [3]

2. Grid Style:

Look: This layout organizes notes and attachments in a grid or table format, with rows and columns.

Example: In a management portal, where users upload documents and notes related to tasks, the Grid Style allows users to see all files and notes in a structured, side-by-side view. [4]

The Attachment feature enables users to upload, organize, and manage file attachments directly within the portal. Admin  can configure settings to control how attachments are displayed and managed: [1]

Attachment Configuration Settings:

– Label: Set as “Attachments” to indicate the section for file attachments.

– Allow Creating Records: Enables users to add new records.

– Button Label: Set as “Create” for adding new attachments.

– Allow Deleting Records: Permits users to delete attachments.

Default Accordion Behavior:

– Expanded: Accordion opens by default.

– Collapsed: Accordion remains closed by default. [2]

Front view Attachment:

On the front side each attachment item could have a small delete icon, allowing users to remove specific attachments if “Allow Deleting Records” is enabled. The default expanded accordion view shows all attached files directly, making it easy for users to view, add, or delete attachments as needed. [3]

If admin are designing a form for an object that includes products, admin can enable the Product widget for any form type in the customer portal. Simply drag and drop the Product widget onto the designated grid area. [1]

Steps to Configure the Product Widget:

1. Accessing the Product Widget:

– When designing a form for an object with associated products, the Product widget will be available.

– Click on the field’s Settings icon to open the Product Configuration panel.

2. Configuration Options:

– Label: Enter the label that will be displayed for the product section on the portal.

– Default Accordion Behavior: Choose how the list view data appears to portal users:

 – Expanded: The section will be open by default.

 – Collapsed: The section will be closed by default. [2]

Example: If admin are creating an order form where users can add products, admin would enable the Product widget, label it as “Order Items,” and configure it so users can add or delete items and adjust quantities directly from the portal. The product section might be set to Expanded so that users see their order items as soon as they open the form.

Front view Product widget:

On the front side each product entry may have options to view details, edit, or delete if permissions allow. The expanded view provides users with an immediate overview of all products, with buttons to quickly add new items or apply filters for easy navigation and management. [3]

Admin  can use the Text widget to add and customize text content within any page layout. This widget allows Admin  to insert and design text with various settings to enhance the appearance and functionality of the portal pages. [1]

Steps to Configure the Text Widget:

1. Adding the Text Widget:

– Simply drag and drop the Text widget onto the designated grid area.

2. Configuring the Text:

– After placing the widget, click on the Settings icon to open the Text Configuration panel.

– Text Content:Insert the desired text that should appear in this section.

– Styling Options: Admin can apply various styling options to the text, such as font size, color, alignment, and formatting (bold, italic, underline).

– Advanced Options: Admin may also have options to add hyperlinks, bullet points, or numbered lists to structure the content effectively. [2]

Example:  If admin creates an “About Us” page, admin can use the Text widget to add a detailed company description. By using the settings, admin can make certain parts of the text bold to highlight key points, adjust the font size for readability, and align the text to center it on the page.

Front view text widget:

Admin  can update this text to display important information, instructions, or any custom message they wish to convey to users. The Text Widget is a simple, customizable area for static content, enhancing user communication within the portal. [3]

The box authentication widget integrates document management into the portal, allowing users to upload files, create new folders, and organize documents directly. Admin  can configure titles, labels for upload and folder creation buttons, and set the default display behavior for ease of use. [1]

Steps to Configure the Box document Widget:

– Title: Set to “Documents” to display a label for document management.

– Upload Button Label: Label as “Upload File” for user-uploaded documents.

– New Folder Button Label: Label as “New Folder” to allow folder creation in SharePoint.

– Default Accordion Behavior:

– Expanded: Accordion is open by default.

– Collapsed: Accordion is closed by default.

Front-view Box Authentication widget:

The ” Documents” title is displayed at the top, followed by buttons for uploading files and creating new folders. The accordion section shows folders and documents, allowing users to navigate and manage their Box document files easily. The accordion is expanded by default, so users can immediately see the contents. [3]

To initiate the creation of a new page, follow these steps:

Page Title: Enter a descriptive and relevant title for the page.  [1]

Page URL Slug: Enter the URL slug determines the page’s address and should be unique and descriptive. Example: portal-dashboard.  [1]

Page Access: Admin can create a page in two ways: 

1. Authenticate: Select this option if the page should be accessible only to users who have logged in.  [1]

2. Public: Choose this option if the page should be visible to everyone without requiring a login.  [1]

Page Layout: Admin can choose from different layouts which is mentioned below: [1]

– Default Layout: Select this to use the standard layout configuration.[1]

–  1 Column, Header, Footer: This layout includes a single column, with a header and footer. Ideal for simple page designs.[1]

– Left Sidebar, Header, Footer: This layout features a left sidebar along with a header and footer, useful for pages that require additional navigation or content sections.[1]