Roles and restrictions
Your role determines which items you can view, create, update, and delete in Flowize. Tag restrictions can further limit which Contents and Flows you can edit or delete, without removing your existing view access.
Roles at a glance
| Role | Summary of access |
|---|---|
| Content Editor | Can create, view, update, and delete contents, conditions, and files. Can view most project and environment settings and upload projects to an environment. |
| Project Admin | Has Content Editor permissions and can manage projects, other project features, environment mapped URLs, and Email Default Channel configurations. Can update and delete existing SMS Default Channel configurations. |
| Full Admin | Has Project Admin permissions and can manage users, project groups, and environments. Can view and update organizations, activate or deactivate workers, and remove projects from an environment. |
| Agent | Has Full Admin permissions and can create and delete organizations, manage Archive, Berichtenbox, and Print Default Channel configurations, and activate or deactivate Default Channels. |
The tables below show the permissions for each role, before tag restrictions are applied. To assign or change a user’s role, see Change user roles.
Permissions by area
All actions means create, read (view), update, and delete. Read only means you can view an item but cannot create, update, or delete it. No access means none of these four actions is permitted.
| Area | Content Editor | Project Admin | Full Admin |
|---|---|---|---|
| Organizations | No access | No access | Read, update |
| Users | Read only | Read only | All actions |
| Project groups | Read only | Read only | All actions |
| Projects | Read only | All actions | All actions |
| Contents, conditions, and files | All actions | All actions | All actions |
| Other project features, including flows, triggers, and data | Read only | All actions | All actions |
| Environments | Read only | Read only | All actions |
| Environment mapped URLs | Read only | All actions | All actions |
Default Channel permissions
Default Channel permissions vary by channel type. Permission to manage a configuration does not automatically include permission to activate or deactivate the channel.
| Default Channel configuration | Content Editor | Project Admin | Full Admin |
|---|---|---|---|
| Read only | All actions | All actions | |
| SMS | Read only | Read, update, delete | Read, update, delete |
| Archive | No access | No access | No access |
| Berichtenbox | No access | No access | No access |
| Read only | Read only | Read only |
None of these roles can create SMS Default Channel configurations. Only the Agent role can activate or deactivate Default Channels.
Additional permissions
| Action | Content Editor | Project Admin | Full Admin |
|---|---|---|---|
| Activate or deactivate workers | No | No | Yes |
| Activate or deactivate Default Channels | No | No | No |
| Upload a project to an environment | Yes | Yes | Yes |
| Remove a project from an environment | No | No | Yes |
Tag restrictions
Tag restrictions apply to all types of Contents and to Flows. Restricted users retain their existing view access, but can only edit or delete items that share at least one of their assigned tags, within the permissions allowed by their role. A matching tag does not grant additional role permissions.
Full admins and project admins can create and edit organization tags and assign them to Contents and Flows.
Only full admins can assign, change or remove tag restrictions for users.
For instructions on assigning tags and configuring restrictions, see Using tags in Flowize, especially Set up tag restrictions for a user.
Was this article helpful?