Access Control
Description
The access control panel gives you fine grained control over access to resources.
Reach the access control panel from the admin drop down:
- Click the Profile Icon in the top right corner
- Select Access Control from the drop down
Select a user from the left hand user pane to define the user's access rights.
API Access
The same rights that control access to elements of the UI also control access to the same aspects of the API.
Create a new user
In the access control panel:
- Click the New User button in the bottom of the user pane
- Enter display name and email address
- Enter and confirm a new password.
- Click Create
Passwords can be changed anytime and are stored securely
The user can later change the password from the admin panel.
Assigned API Keys
Create or revoke API keys for the user.
Create an API Key for a user by clicking the + button under API Keys. In a similar way you can revoke an API Key for a user by clicking the secondary action ... button and click Revoke API Key.
Assigned projects
Assign projects to a user by clicking the + button under Assigned Projects and select a project.
Access rights and roles
Access rights can be defined for entities such as projects, flows, lexicons, playbooks down to fine grained flow properties such as Basic or Advanced flow nodes.
For each item, the privilege to execute a create, read, update or delete (CRUD) actions can be set in a role based manner. A role is a set of privileges for the a user assigned to it. Roles assigned to a user define the access control list (ACL) displayed under Access Rights and are updated immediately.
The following default roles are available:
Role | Description |
|---|---|
Admin | Admins have unlimited access to anything inside their organisation. In a new installation, the system will create one user with this role. A platform owner should create a new user with this role and delete the automatically created one on first login. |
Basic | The Basic role can view most entities in the system. Once a new user is created within the system, this role will get assigned automatically. |
Marketer | The Marketer role has all permissions the Basic role has, plus:
|
Advanced Editor | The Advanced Editor has all permissions the Marketer has, plus:
|
Developer | The Developer has all permission the Advanced Editor has, plus:
|
In addition to the mentioned default roles, we have the following more-specific roles which can be assigned in addition to any of the default roles:
Project Admin | Adds the following permissions:
|
|---|---|
Basic Flow Editor | Adds the following permissions:
|
Advanced Flow Editor | Inherits everything from the Basic Flow Editor, plus:
|
Custom modules editor | Adds the following permissions:
|
Custom modules admin | Adds the following permissions:
|
Intent editor | Adds the following permissions:
|
Lexicon editor | Adds the following permissions:
|
Lexicon admin | Adds the following permissions:
|
Playbook editor | Adds the following permissions:
|
Playbook admin | Adds the following permissions:
|
Form / Process editor | Adds the following permissions:
|
Form / Process admin | Adds the following permissions:
|
Endpoint admin | Adds the following permissions:
|
NLP Connector admin | Adds the following permissions:
|
Database connections admin | Adds the following permissions:
|
Logs | Adds the following permissions:
|
Conversations | Adds the following permissions:
|
ApiKey user | Adds the following permissions:
|
Userprofile / Contactprofile viewer | Adds the following permissions:
|
Userprofile / Contactprofile editor | Adds the following permissions:
|
Userprofile / Contactprofile admin | Adds the following permissions:
|
ODATA | Adds the following permissions:
|
Analytics | Adds the following permissions:
|
Packaging admin | Adds the following permissions:
|
Secrets basic | Adds the following permissions:
|
Secrets editor | Adds the following permissions:
|
Secrets admin | Adds the following permissions:
|
Livechat | Adds the following permissions:
|
Updated about 2 years ago