Portal contexts

Portal context engine allows restricting access to specified portals for some user categories defined by User Criteria. 

Example case:

  1. You create two portals: Moscow Users Portal and London Users Portal.
  2. You need to restrict access to these portals only for users from relevant cities.
  3. Using the portal contexts engine, you can easily do this by creating a user criteria record (in this case, you have to specify the location as a criterion).


Role required: admin.


Before you start, you need to create the necessary user criteria first. For information on how to create them, please refer to the User Criteria article.


To create a portal context, please complete the steps below:

  1. Navigate to Portal Structure → Context Rules → Portal Contexts
  2. Click New and fill in the fields.
  3. Click Save or Save and Exit to apply changes.

Portal context form description

FieldMandatoryDescription
PortalY

Specify a portal to which you need to restrict access.

You can create only one portal context record per one portal.


Active
Select this checkbox to make this portal context record active.
Audience CriteriaNIn this field, select user criteria to define users who will have access to the portal specified. If no criteria were specified, then this portal will be accessible for all users.
OrderN

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 him.


Related properties

  1. 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'.
  2. You can define roles whose owners 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.

The admin role is already preconfigured for portal context overriding.

Page mappings

The page mappings engine is used to configure redirect rules in case if the visited link is not accessible for the user due to role restrictions.

Example case:

  1. One user sent a task link to another. The task link leads to the administrative interface and looks like this: (https://instance.example.com/record/task/16850930533524).
  2. The other user does not have an agent role, so he will not be able to open it correctly. But he can open portal links, respectively.
  3. The page mappings engine allows creating a rule which will convert administrative interface links to portal links.
  4. After processing with a rule, the initial link looks like this:
    1. https://instance.example.com/portal/record/?table_name=task&record_id=16850930533524&view=SP
  5. Now, the link recipient can see the link content.


Role required: admin.

To create a page mapping rule from scratch, please complete the steps below:

  1. Navigate to Portal Structure → Context Rules → Page Mappings.
  2. Click New and fill in the fields.
  3. Click Save or Save and Exit to apply changes.

It is more effective to create page mapping rules out of the portal context rules. For this, navigate to the relevant portal context record, open the 


FieldMandatoryDescription
Portal ContextYSpecify a reference to the previously created portal context.
URL TemplateY

Specify initial URL template. You can use variables here.

Examples:

record/task/{id}

{controller}/{essence}/{id}

Portal PageY

Specify portal page URL template. This template is used to create URLs for portal pages out of URLs passed.

Example:

/portal/record/?table_name=task&record_id={id}&view=SP