Roles are used within T6 to restrict or allow access in specific cube contexts. We can also define whether the user will have read and write access, or only read access, within these contexts in the form. This makes it possible for different users to have broader or more restricted views of the information contained in the same form.
A Role is an excellent way to restrict access in forms. However, this feature should be used with caution, as the more restrictions defined, the longer it will take to load the forms.
Roles will only be applied if the Create and view data entry forms functionality is disabled for the user in the Manager profile functionalities.
To create and edit roles in T6, we will need to have certain Features enabled:
A user can only grant permissions in roles they own or have permissions for.
Through roles, we can perform the following functions:
To create a new role in T6, follow these steps:
;Name: Name of the role, which will be displayed in the explorer listing;
Description: Description of the role, which will be displayed in the explorer listing;
Application: Select the application to be linked to the role;
Permissions: Select one of the following options:
The user needs a role to be able to view the data of the application forms; we must have at least one role granting read and write permission to the users who will use the form.
If we use the allow read and write permission and include a member, the system will automatically grant permission only to the selected member, and restrict all others. That is, if we want to allow read and write, we do not need to specify any member in any dimension, just save the role blank. Then we will add other roles for restrictions.
If read and write are denied for a specific member, all other members will automatically be allowed.
If we do not have a role allowing read and write in the application and allow read and write for a specific member, all other members will automatically be restricted from viewing and editing.
Restriction roles will always override permission roles.
In Static Roles, we will have the context in table form, where we will select the dimensions and the members to be linked to the role;
;
;
;
, and the following options will be displayed:| Aggregation | Description |
|---|---|
| Member | Selects only the reference member |
| Descendants | Selects all descendants of the reference member |
| Descendants (inc) | Selects all descendants of the reference member, including itself |
| Ancestors | Selects all ancestors of the reference member |
| Previous | Selects the directly preceding member in the member tree, at the same level as the reference member |
| Next | Selects the directly following member in the member tree, at the same level as the reference member |
| Previous (Relative to the parent) | Selects the previous member at the same level and relative to the parent of the reference member |
| Ancestors (inc) | Selects all ancestors of the reference member, including itself |
| Same Level Members | Selects all members at the same level as the reference member |
| Same Level Members (inc) | Selects all members at the same level as the reference member, including itself |
| Parent Member | Selects the parent of the reference member |
| Next (Relative to the parent) | Selects the next member at the same level and relative to the parent of the reference member |
| Previous (Relative to the root) | Selects the previous member in the member tree, at the same level and relative to the root of the member tree |
| Next (Relative to the root) | Selects the next member in the member tree, at the same level and relative to the root of the member tree |
| Parent Member (inc) | Selects the parent of the reference member, including itself |
| Children Member | Selects the children of the reference member |
| Children Member (inc) | Selects the children of the reference member, including itself |
| Descendants without children | Selects all leaf descendants (those without children) of the reference member |
| Previous members same root (inc) | Selects the previous members in the member tree, at the same level and under the same root as the reference member |
| Next members same root (inc) | Selects the next members in the member tree, at the same level and under the same root as the reference member |
| Previous members same amount children root (inc) | Selects the previous members of the reference member, under the same root and with the same number of children |
| Data Member | Selects only the Data Member of the selected member |
| Descendant Data Members (inc) | Selects all Data Members descendants of the reference member, including its own Data Member |
| Exclude Member | Excludes the reference member |
| Exclude Data Member | Excludes the Data Member of the reference member |
| Next members same amount children root (inc) | Selects the next members of the reference member, under the same root and with the same number of children |
| Children [Words-DataMember] | Selects only the Data Member children of the selected member |
By default, the aggregation will be set to Member.
;
In Dynamic Roles, we will need to select a data table. The existing contexts in the selected table will be displayed, and we will select the contexts and columns to be linked to the role;
;To associate a role with a user, follow these steps:
Select the role you want to associate and click on
;
A side panel will open, where we will select Users;
and the available users for selection will be displayed;After selecting the users to be associated with the role, click on
again;
To finish, click on
.
To remove users from a role, follow these steps:
Select the role from which you want to remove users and click on
;
A side panel will open, where we will select Users;
, where the users associated with the role will have the checkbox enabled;After selecting the users to be removed from the role, click on
again;
To finish, click on
.
Only users who have permission in the application selected in the role and users the logged-in user has permission to view will be displayed in the list.
To associate a role with a group, follow these steps:
Select the role you want to associate and click on
;
A side panel will open, where we will select Groups;
and the available groups for selection will be displayed;After selecting the groups to be associated with the role, click on
again;
To finish, click on
.
To remove groups from a role, follow these steps:
Select the role from which you want to remove groups and click on
;
A side panel will open, where we will select Groups;
, where the groups associated with the role will have the checkbox enabled;After selecting the groups to be removed from the role, click on
again;
To finish, click on
.
Roles are used to restrict or allow access in specific cube contexts, defining whether the user will have read and write access, or read-only access, within forms.
To create and edit roles, the user must have the following features enabled:
From Administrator: Manage the security of the application (full) (multi-app) and Manage System Users.
From Manager: Manage Application Security.
The greater the restrictions defined in roles, the longer form loading time will be, so they should be used with caution.
No, a user can only grant permissions in roles they own or have permissions for.
There are 5 permission types that can be configured in roles:
The Allow Read and Write permission in roles works as follows:
If any member is included, the system will automatically grant permission only to the selected member and restrict all others.
To allow all members, do not specify any member in any dimension.
When a role uses Deny Read and Write on a specific member, access to that member is automatically blocked, while all other members are allowed.
When there is a conflict between permission and restriction roles, Restriction Roles always override permission roles.
The difference between the two role types is how the context is selected.
Static Roles use a table-based context where you select dimensions and members;
Dynamic Roles use a data table where you select contexts and table columns.
There are more than 20 aggregation options available for selection in static roles. All options are listed below:
| Aggregation | Aggregation | Aggregation | Aggregation |
|---|---|---|---|
| Member | Descendants | Descendants(inc) | Ancestors |
| Previous | Next | Previous(relative to parent) | Ancestors(inc) |
| Same level members | Same level members(inc) | Parent member | Next(relative to parent) |
| Previous(relative to root) | Next(relative to root) | Parent member(inc) | Children member |
| Children member(inc) | Descendants without children | Previous same root(inc) | Next same root(inc) |
| Previous same amount children root(inc) | Data member | Descendants data member(inc) | Exclude member |
| Exclude data member | Next same amount children root(inc) | Children data member |
To associate users with a role, the role must already exist. Follow the steps below:
Yes, but to add groups to roles, the role must already exist. Follow the steps below:
To create a new role, follow the steps below:
After creating the role, you can associate users and/or groups with it.