Skip to main content
Each backend administrator can be assigned a subset of permissions to limit their access to only the areas they need. Permissions are set per-user from Settings > Curator > Backend Administrators. Some permissions are only visible when certain features or integrations are enabled on your Curator instance. So in case you don’t see the corresponding menu item on the left-hand navigation, it is because you don’t have that feature currently enabled.

Central Dispatch

Content

Data Manager

Integration

Security

Curator

MCP Tokens

MCP tokens need no dedicated permission. Every backend user can generate, edit, and revoke their own tokens from MCP Tokens in the username dropdown. A token can only do what its owner can do, and each MCP tool checks the owner’s permissions when it runs. The MCP tools that change content use the existing permissions: Manage Pages for pages, Manage Navigation for menu items, Manage Files for files, Manage Curator Settings for themes, and Manage API Keys for REST API keys. See MCP.

Power BI

Sigma

Tableau

ThoughtSpot

Translator

User Management

Granting Permissions to Other Administrators

An administrator who is not a superuser can only grant permissions they hold themselves. The Backend Administrators form lists only those permissions, and any other permission already on the account being edited stays as it is. To change a permission you do not hold, ask an administrator who holds it, or a superuser.

Superuser Accounts

Apart from the permissions on this page, a backend administrator account can be a Superuser, such as the first administrator account created when Curator was installed. A superuser can access every area of the backend, whatever permissions are checked on its account. Superuser accounts are protected. Only another superuser can edit, delete, restore, unsuspend, or reset the password of a superuser account. An administrator who is not a superuser gets this error when trying to change one, even with every permission checked, including Manage Backend Users:
The Backend Administrators page does not show or change whether an account is a superuser, so checking more permissions will not clear this error. No administrator can change their own superuser status or their own permissions either. To remove a former employee’s superuser account, sign in with another superuser account and delete it from Settings > Curator > Backend Administrators. If nobody in your organization can sign in with a superuser account, contact InterWorks Support.

System