Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Tip |
---|
Role required: admin. |
Portal contexts
The portal context engine allows you to restrict access to specified portals for some user categories defined by User Criteria.
Example:
- You create two portals: Moscow Users Portal and London Users Portal.
- You need to restrict access to these portals only for users from relevant cities.
- Using the portal contexts engine, you can easily do so by creating a user criteria record (in this case, you have to specify the location as a criterion).
Create a portal context
Note |
---|
Before you start, you need to create the necessary user criteria first. For more information, see the User Criteria article. |
To create a portal context, complete the steps below:
- Navigate to Portal Structure → Context Rules → Portal Contexts.
- Click New and fill in the fields.
- Click Save or Save and exit to apply the changes.
Portal Context form fields
Field | Mandatory | Description | ||
---|---|---|---|---|
Portal | + | Specify a portal to which you need to restrict access.
| ||
Active | - | Select this checkbox to make this portal context record active. | ||
Audience criteria | - | In this field, select user criteria to define users who will have access to the portal specified. If no criteria are specified, this portal will be available to all users. | ||
Order | - | Specify a portal context record processing order. If some user fits more than one portal context record, then a record with the lesser Order value is applied to the user. |
Related properties
- You can enable or disable this engine by editing the portals.portal_context.enable property value. It is disabled by default. To enable portal context, edit the property value and type 'true'.
- You can define roles, the owners of which disregard portal context rules and have access to all categories and items of the portal specified. For this, edit the portals.portal_conteхt.override_roles property value and specify roles here.
Note |
---|
Users with the admin role can always access any portal. The setting is preconfigured for portal context overriding. |
Page mapping
The page mappings engine is used to configure redirect rules in case the visited link is not accessible due to role restrictions.
Example:
- One user sent a task link to another. The task link leads to the agent interface and looks the following way: https://instance.example.com/record/task/162306286418042670.
- The other user does not have an agent role, so they will not be able to open and see the task record. But they can open portal links, respectively.
- The page mappings engine allows you to create a rule that will convert agent interface links to portal links.
- After processing with a rule, the initial link looks the following way:
https://instance.example.com/portal/record/?table_name=task&record_id=162306286418042670&view=SP - Now, the link recipient can see the link content.
Create a page mapping
To create a page mapping rule from scratch, complete the steps below:
- Navigate to Portal Structure → Context Rules → Page Mappings.
- Click New and fill in the fields.
- Click Save or Save and exit to apply the changes.
Page Mapping form fields
Field | Mandatory | Description | ||||
---|---|---|---|---|---|---|
Portal context | + | Specify a reference to the previously created portal context. | ||||
URL template | + | Specify initial URL template.
You can use variables here. Example: /record/{tableName}/{recordID}
| ||||
Portal page | + | Specify portal page URL template. This template is used to create URLs for portal pages out of URLs passed.
Example: /portal/record?table_name={tableName}&record_id={recordID}&view=SP |
.
Table of Contents | ||||||
---|---|---|---|---|---|---|
|
Panel |
---|
Related articles |