Permissions
When setting up your team in Kontent.ai, you create roles in your project and choose from several permissions. Each permission defines what your users can do within a project.This reference explains what each permission enables users to do.
Content production
Role permissions can be further refined by assigning roles in specific collections.Content item permissions
The View permission allows users to:- View content items in the project.
- Move content items through their workflow (also depends on your workflow setup).
- Publish content items.
- Unpublish and archive content.
- Cancel scheduled content items.
- View and compare older versions of content items.
- Assign contributors to content items.
- Set due dates for content items.
- Add notes.
- Add comments and suggestions.
- Add, edit, delete, and resolve tasks.
- Access Mission Control, which also includes Project overview and Editorial calendar tabs.
- Access the Relations tab.
- Edit content items.
- Work with item versions (also depends on your workflow setup).
- Create new versions of content items.
- Restore older versions of content items.
- Discard the latest versions of content items.
- Work with custom elements used in content items.
- Insert components to content items.
- Approve suggestions.
- Move items between collections.
- Create new content items.
- Duplicate content items.
- Create new language variants of content items.
- Convert components to items.
Asset permissions
The View permission allows users to:- View assets in the project.
- Create customized versions of assets in content items.
- Modify asset descriptions.
- Assign assets to collections.
- Assign taxonomy terms to assets.
- Edit asset codenames.
- Create folders.
- Upload new assets to the asset library.
Restrict access to specific content
You can allow users to work with all content or only the content items assigned to them. The role can be further defined by setting which specific content types and content groups the role can work with. If there are specific content types and content groups that you don’t want the role to work with, exceptions can be added to the role.Active permissions and workflows
The content capabilities of a given role can be further restricted by your project's content workflows setup. For each workflow step, you can limit which roles can work on content in the given step and move it to the following steps. For example, if you want only Project managers to be able to publish content:- Set up your workflow steps so that only a single step transitions to the Published step; for example, a step named Approved.
- Limit the Approved workflow step to the Project manager user role.
Content model
The Manage content types, asset type, and snippets permission allows users to:- View content types, content type snippets, and asset type.
- Add, modify, and delete content types.
- Add, modify, and delete content type snippets.
- Duplicate content types.
- Add, modify, and delete the asset type.
- View taxonomy groups and terms.
- Add, modify, and delete taxonomy groups and terms.
- Add, modify, and delete sitemap items.
Settings
The Manage environment permission allows users to:- Create new environments.
- Manage environments.
- Delete the environments in which the users are active.
- Add, modify, and delete custom roles.
- View the content workflow settings.
- Add, modify, and delete workflows and their workflow steps.
- Reorder steps in workflows.
- Add, modify, and delete spaces.
- View and configure collection settings.
- View the localization settings.
- Add and configure project languages.
- Create their own personal API key.
- View the personal API key in Project settings.
- View and modify the codenames of content items.
- View and modify preview URLs.
- View, add, modify, and delete webhooks.
- Set a default Home item in the Relations tab for every user in the environment.
- View activity logs in the audit log.
- View the custom app settings.
- Add, modify, and delete custom apps.