Overview of User Roles
About User Roles
Conversational AI Cloud has several user roles defined at a system level, which allows an administrator to set a role for a user for a project. For each individual project, a user can have only one role. If a user has access to multiple projects, it's possible for them to have different roles for different projects.
User roles are only available for the Enterprise package.
For content roles the development path (and roles) are typically in this order:
- Basic Content Editor > New to Conversational AI Cloud
- Content Editor > Experienced user of Conversational AI Cloud
- Content Engineer > Very experienced user of Conversational AI Cloud with permission to import content
Note: When you go up a level with the content role, the previous content role should be removed.
Access to parts of Conversational AI Cloud is controlled based on the role as shown in the table below.
The access rights are described as C-R-U-D:
C = Create
R = Read
U = Update
D = Delete
* User role may not have access to certain tasks & dashboards.
access / roles | BI viewer | Articles only | Basic Content Editor | Basic Content Editor (+ labels) | Content Editor (no labels) | Content Editor | Content Engineer |
Tasks | | | R* | R | CRUD | CRUD | CRUD |
Articles (Q&A) | | CRUD | CRUD | CRUD | CRUD | CRUD | CRUD |
Events | | | | | CRUD | CRUD | CRUD |
Dialogs | | | CRUD | CRUD | CRUD | CRUD | CRUD |
Entities | | | | | CRUD | CRUD | CRUD |
Reg. Expressions (Regex) | | | | | R | R | R |
Labels | | | | CRUD | | CRUD | CRUD |
Test | | R | R | R | R | R | R |
Dashboards | R | R* | R* | R* | R | R | R |
Additional Roles
Any of the additional roles listed here can be applied to one of the user roles by the Admin.
Additional roles | Description |
Project Publisher | Has the right to publish project |
ContextStore Editor | Can access APIs to change session and user related contexts |
Workflow Administrator | User can change content without it having to be approved and can approve/reject content changes from other team members. |
External JavaScript Developer | Can manage transactional dialogs, webhooks, user and session properties and regex (via the entities screen). Note: that this user role must be combined with one of the Content Editor roles or the user might experience issues while trying to log into Conversational AI Cloud |
Roles Giving Access to the Configuration Screen (Enterprise)
Content Engineer | External JavaScript Developer | |
Project constants | CRUD | * |
Metadata (Additions) | CRUD | * |
User properties | R | CRUD |
Webhooks | CRUD | |
Context variables | CRUD | * |
autoDialogs (Beta) | RU | * |
*External JavaScript Developers must also have a Content Editor user role to be able to access the CMS. If they have the Content Engineer User role, they will have access to other configuration types, otherwise they will only see the types listed in the table.
Managing CMS Users With Multiple Roles (Enterprise)
When changing roles for a user, always be sure to remove the previous role. If your CMS users have overlapping content roles, it can potentially cause them to experience issues while working in Conversational AI Cloud.
An overlapping role would be a user with the combination of any two “content editor” type roles from the Conversational AI Cloud User Roles table, for example:
- Basic Content Editor + Content Editor
- Content Editor + Content Engineer
Note: A user role from the Conversational AI Cloud User Roles table can always be combined with a role from the Additional Roles table.
Related Articles
Where can I manage the users for my project?
How do I change a CMS user role?
