Permission management

Before, a Settings-ID had a set of email addresses that could equally access this Settings-ID. This meant that everyone involved was an admin and each and every Settings-ID had to be managed separately. With the rollout of role and permission system, two new entities are introduced that affect this status-quo.

The first entity is for creating companies; a company will have a name and address. A Settings-ID can be assigned to only one company at a time. Currently, a clustering of companies is not possible.

The second entity is for permissions management; permissions determine what a logged-in user can and cannot do within the admin interface.

ADMIN access, WRITE access, and READ access are introduced under this entity. Permissions can be for a company or just for a Settings-ID. It is important to note that permissions are automatically inherited from the company level to the Settings-ID level unless otherwise overwritten.

A user with ADMIN access to a company can:

• edit company details
• delete a company
• manage company permissions
• assign(remove) Settings-IDs to(from) a company
• configure all Settings-IDs assigned to a company

A user with WRITE access to a company can:

• configure all Settings-IDs assigned to a company

A user with READ access to a company can:

• see all Settings-IDs assigned to a company

A user with ADMIN access to a Settings-ID can:

• manage permissions for this Settings-ID
• overwrite permissions inherited from the company for a specific user for this Settings-ID
• configure this Settings-ID
• publish this Settings-ID
• download reports for this Settings-ID

A user with WRITE access to a Settings-ID can:

• configure this Settings-ID
• publish this Settings-ID
• download reports for this Settings-ID

A user with READ access to a Settings-ID can:

• see the configuration for this Settings-ID
• download reports for this Settings-ID

All users will see the option to create new companies. But, no user can create new Settings-IDs; the users are advised to get in touch with their point of contact at Usercentrics (as before) for a new Settings-ID.

This user does not necessarily have to be a user at the company level.

No, this user can only know the company this Settings-ID is assigned to.

Yes, only if the admins of this company did manually overwrite the said user’s inherited WRITE Settings-ID permissions accordingly.

Yes, this is possible only if both the users have ADMIN access to the same company, i.e., one admin’s status can only be changed by another relevant admin (and not by the same admin). The logic is the same for admins at a Settings-ID level as well.

There is no limit to the number of admins possible at both levels.

Any user of this Settings-ID with ADMIN access to a company can assign this previously unassigned Settings-ID to that company. As the user is an admin of the company, this particular user then also becomes the admin of this newly assigned Settings-ID.

The other users with direct access are processed depending on the following conditions:

• The attached setting was not used in the new Permission System before: all other users will have WRITE permission on the setting.
• The attached setting was used in the new Permission System before: all other users keep their current direct permissions on the setting

The company administrator who removes the setting will become the direct administrator of the setting. Other members of the company will not have access to the setting anymore, however, users that might have direct access to the setting can still access it.

A user that is removed from a company will also be removed from any direct access to a setting. If you want to make sure a user without company access has no direct access anymore, you can also add this user to your company and directly remove the user again.

This feature is not implemented in the current version.

This feature is not implemented in the current version.

There are 3 kinds of permissions that can be assigned to a user of the company:

ADMIN

• Add or remove settings from the company
• Manage permissions for the company and settings
• Full access to all settings belonging to the company: permissions for settings can be managed from permission management service whereas all other configurations related to the settings can be done from the setting itself
• You cannot remove admin permission from yourself. Only another admin can change that

WRITE

• Full access to all settings belonging to the company: permissions for settings can be managed from permission management service whereas all other configurations related to the settings can be done from the setting itself

READ

• View all settings assigned to the company

Select settings to be added under this company and click on “Finish.”