In the Management Portal at Setup > Administrative Roles, prevent unauthorized access to the Management Portal and Setup and Sync Tool. On the Administrative Roles tab, configure the permissions of an administrative role. This determines what the login account to which it is assigned is allowed to do.
Explanation and Tips
For each administrative role, you can set different permissions on the functionality of the Management Portal and Setup and Sync Tool:
Select Deny to hide the item. By default, the access permissions of a new administrative role are set to Deny.
Select Read to set read-only access (available for services, people, organizational context and data connections).
Select Modify to grant full access.
Select Inherit (blank) to let items inherit the access permissions of their parent (available for data connections, organizational context and services). You can also set explicit access permissions for these items that deviate from the permissions of the "parent".
In the section Attribute Value Visibility, specify permissions to modify restricted information in text and table service attributes, text and table people attributes and people identifiers. This includes any related placeholders. These values are shown as to administrators with insufficient permissions to view restricted information. This functionality applies to the Management Portal only; restricted information is still shown in the Web Portal.
The Building Block functionality is only available if your login account has been assigned the administrative role Full Access. Other administrative roles, including ones that grant Modify access to all functionality, do not grant access to the Building Block functionality.
Similarly, you can only synchronize data connections via a command line if your login account has been assigned the administrative role Full Access.
Multiple administrative roles
If you assign multiple administrative roles to a login account, the permissions of all roles are combined, in which the least restrictive permissions apply:
Modify takes precedence over Read and Deny
Read takes precedence over Deny
Administrative role 1 has Deny permissions on a specific service A.
In administrative role 2, service A inherits Modify permissions from the service category.
Result: A login account that is assigned both administrative roles 1 and 2 gets Modify permissions on service A.
Administrative role 1 has Modify permissions on the Service Catalog page.
Administrative role 2 has Read permissions on the Service Catalog page.
Result: A login account with roles 1 and 2 gets Modify permissions on the Service Catalog page.