Entities Portal Visibility
For the management of modules related to the End-User Portal, it is possible to intervene through configuration to change the display/management of the modules directly from the “Configuration” section of the “System” menu:
By clicking on “Portal Configurations” you will be able to manage the following modules:
Activity – Worklog visibility
For the visibility of the Activity module in the Deepser user portal, it is possible to act by configuration by going to “SYSTEM > Configuration > Portal – Configurations” and finally Activity, we will access the Deepser section dedicated to configuring the visibility of the Activity module on the portal side:
Inside we will find the following configurable fields:
- Show Worklogs: Which allows you to view worklog records on the end-user portal side.
- Add/Edit Worklogs: Which allows end users to edit or add new worklogs.
Worklog visibility is based on the entity it relates to. If the user has visibility for that specific entity then he can also see the worklogs if added to the form template.
CMDB – CIs Visibility
For the visibility of CIs in the Deepser user portal, we can act in different ways.
First of all, going to “SYSTEM > Configuration > Portal – Configurations” and finally CMDB, we will access the section of Deepser dedicated to configuring the visibility of the CMDB on the portal side:
From here we can act on the configuration:
Enable: Allows you to enable or disable the visibility of the CMDB on the portal side.
Enable Priority: Allows you to choose how you want to manage the visibility of your CIs on the portal side.
The selectable values will be:
- Global: Which allows the CMDB module to be displayed to all end users without distinction.
- Users: Which allows the CMDB module to be displayed only to end users who have the “Portal CMDB Visibility” field set to “Yes” in their master data (accessible from System > Permissions > Users).
Once the CMDB module display type has been enabled and configured, the display of individual CI records will be managed based on the following fields:
- Owner Company – if the company of the user is the owner company
- Owner Group – if the user is part of the owner group
- Assigned User – if the user is assigned user for that entity
- Status – if the status of the entity is active
CRM – CRM Modules Visibility
For the visibility of CRM modules in the Deepser user portal, it is possible to act by configuring by going to “SYSTEM > Configuration > Portal – Configurations” and finally CRM, we will access the Deepser section dedicated to configuring the visibility of the CRM on the portal side:
From here it will be possible to indicate which modules in the CRM section must be made visible on the portal side (Enable Account, Enable Contact, Enable Opportunities fields).
You can also specify which groups will be able to access these modules, or whether all users will be able to access them indiscriminately (by selecting All groups).
Once the CRM forms section is enabled and configured, the display of individual records will be managed according to the “Portal Visibility” field in the reference form. Then the records will be displayed respecting the value of the following fields:
- Portal Visibility = Yes
- Linked Company – if the user company is the same as the linked company of the entity
- Parent Company – if the user company is the same as the partner company of the entity
- Owner User – if the user is the owner of the entity
Knowledge Base Visibility
For the visibility of the Knowledge Base in the Deepser user portal, it is possible to act by configuration by going to “SYSTEM > Configuration > Portal – Configurations” and finally Knowledge Base, we will access the Deepser section dedicated to configuring the visibility of the Knowledge Base module on the portal side:
Once the KB module view is enabled and configured, the display of individual records will be managed according to the “Portal Visibility” and “Kb Group View” fields present in the Knowledge Base record configuration:
In addition, it is possible to intervene on the visibility of a single article in the KB always through the “Portal Visibility” field present within the article:
If the “Portal Visibility” field is set to “Yes”, the knowledge base or article will be displayed on the portal side.
Password Visibility
For the visibility of CRM modules in the Deepser user portal, it is possible to act through configuration by going to “SYSTEM > Configuration > Portal – Configurations” and finally Password, we will access the Deepser section dedicated to configuring the visibility of Passwords on the portal side:
From here it will be possible to enable the display of the Password module on the portal side through the “Enable” field.
You can also specify which groups will be able to access these forms or whether all users will be able to access them indiscriminately (by selecting All Groups) via the “Enabled Groups” field.
Once the Password module is enabled and configured, the display of individual records will be managed based on the following fields:
- View Groups – if user is part of the group he can only see and not edit the entity
- View and Edit Groups – if user is part of the group he can see and edit the entity
- Use Groups – if user is part of the group, he can use the password if provided in other entity like field.
- View User – if the user is selected, he can only see the entity
- View and Edit User – if the user is selected, he can see and edit the entity
- Use User – if the user is selected, he can use the password if provided in other entity like field.
- Company – if user’s company is selected, he can see the entity
Anyway, an end-user can only save private passwords. So, all passwords saved from end-user portal couldn’t be visible in the backend, but there are available only for him.
Approval Visibility
For the visibility of approvals, in the Deepser user portal it is possible to act by configuration by going to “SYSTEM > Configuration > Portal – Configurations” and finally Approval, we will access the Deepser section dedicated to configuring the visibility of the Approval module:
Inside we will find the “Enable” field as configurable. If enabled, it will allow the use of portal-side approvals.
However, a requirement for using portal-side approvals is the use of end-user Empowered licenses.
Only these types of users will have the ability to use the approvals module.
Survey Visibility
For the visibility of Surveys, in the Deepser user portal it is possible to act by configuration by going to “SYSTEM > Configuration > Portal – Configurations” and finally Survey, we will access the Deepser section dedicated to configuring the visibility of the Survey module:
Inside we will find the following configurable fields:
- Enable: Which allows you to view portal-side survey records.
- Enabled Groups: If the module is enabled via the “Enable” field, through this field it is possible to enable the visibility of the surveys to selected groups (or to all users by selecting “All Groups”).
The visibility of a single survey on the portal side will be managed based on the enhancement of the “Users” and “Groups” fields present within the survey.
Task Visibility
For the visibility of the Activity module in the Deepser user portal, it is possible to act by configuring it by going to “SYSTEM > Configuration > Portal – Configurations” and finally Tasks, we will access the Deepser section dedicated to configuring the visibility of the Task module on the portal side:
Inside we will find the following configurable fields:
- Enable: Which allows you to view portal-side task type records.
- Enabled Groups: If the module is enabled via the “Enable” field, through this field it is possible to enable the visibility of the tasks to the selected groups (or to all users by selecting “All Groups”.
The visibility of the tasks will instead be based on the “Portal Visibility” field present within the task and which must be set to “Yes” to make the portal task visible and the related “Assigned User” and “Assigned Groups” fields to be enhanced according to the users or user to whom the task is to be visible.
Project Visibility
For the visibility of the tasks of the project module, in the Deepser user portal it is possible to act by configuration by going to “SYSTEM > Configuration > Portal – Configurations” and finally Project, we will access the Deepser section dedicated to configuring the visibility of project tasks on the portal side:
Inside we will find the following configurable fields:
- Enable: Which allows you to view portal-side task type records.
- Enabled Groups: If the module is enabled via the “Enable” field, through this field it is possible to enable the visibility of the tasks to the selected groups (or to all users by selecting “All Groups”.
The visibility of the tasks will instead be based on the “Portal Visibility” field present within the task and which must be set to “Yes” to make the portal task visible and the related “Assigned User” and “Assigned Groups” fields to be enhanced according to the users or user to whom the task is to be visible.
