Role permission reference

When setting up your team in Kontent, you create roles in your project and choose from several permissions. Each permission defines what your users can do within a project.

This reference lists what each permission enables users to do.

Content production

The View ‌permission allows users to:

• View content items in the project.
• Move content items through their workflow (also depends on your workflow setup).
  • 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, and resolve tasks.
• Access Your content, Project overview, and Editorial calendar tabs.
• Access the Relations tab.

The Edit ‌permission allows users to:

• 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.
• View all assets in the project.
• Add, modify, and delete assets.

The Create ‌permission allows users to:

• Create new content items.
• Duplicate content items.
• Create new language variants of content items.
• Convert components to items.

The Delete ‌permission allows users to:

• Delete content items.

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 workflow

The content capabilities of a given role can be further restricted by your project's content workflow setup. For each step in the workflow, you can limit which roles can work on content in a given workflow step and move it to the following steps.

For example, if you want only Project managers to be able to publish content:

1. Set up your workflow steps so that only a single step transitions to the Published step, for example a step named Approved.
2. Limit the Approved workflow step to the Project manager user role.

For a more thorough example of using roles and workflow together, see Setting up a common production flow.

Content models

The Manage content types and content type snippets permission allows users to:

• View content types and content type snippets.
• Add, modify, and delete content types.
• Add, modify, and delete content type snippets.
• Duplicate content types.

The Manage taxonomy permission allows users to:

• View taxonomy groups and terms.
• Add, modify, and delete taxonomy groups and terms.

The Manage sitemap permission allows users to:

• Add, modify, and delete sitemap items.

Development

The Manage APIs permission allows users to:

• View API keys and use the Kentico Kontent APIs.

The Manage development settings permission allows users to:

• View and modify the codenames of content items.
• View and modify preview URLs.
• View, add, modify, and delete webhooks.

The Manage environments permission allow users to:

• Create, manage, and delete environments for the project.
• Manage content and models in the non-production environments. 

Project

The Manage localization permission allows users to:

• View the project's localization settings.
• Add and configure project languages.

The Manage workflow steps permission allows users to:

• View the project's content workflow settings.
• Add, modify, and delete workflow steps.
• Reorder workflow steps.

The Invite and manage team members permission allows users to:

• Inviting and deactivating users.
• Assign roles to users on the project.

The Manage custom roles permission allows users to:

• Add, modify, and delete custom roles.

What's next?

Set up a common production flow for your project and see how roles and content workflow can work together to your team's benefit.