Roles & Permissions
There are some different roles available when adding a user:
Admin
Member
Forms
Read Only
Let's take a look at how these are defined.
Disclaimer: This article will be updated as Role functionality will be added over time
Admin
The Admin role is for the super user who will have access permissions to everything in their organization. They can do the following at the top level organization:
Add and remove Users
Add user Roles
View, edit, and build workflows
Check Results
Add, edit, and configure forms
Manage integrations and organization variables
Create a test user that can Create, Read, Update, and Delete
This is similar to user impersonation without requiring a real user
Create custom roles based on the following default permissions:
rewst.view
rewst.edit
rewst.admin_access
rewst.form.view
rewst.app_platform.view
Additional Create, Read, Update, Delete granular permissions
An Admin will be able to see all of the customer organizations and manage information there. At the customer level, An Admin will be able to access the same information for the customer organization.
Member
The Member role can do the following in the Member's organization:
Add and remove Users
View, edit, and build workflows
Check Results
Add, edit, and configure forms
Manage integrations and organization variables
Forms
The primary use case for this permission level is to provide customers or internal employees with a way to fill out forms. A user with the Forms Role will only have access to form URLs that are provided to them by an Admin or Member. This means they will not have access to the platform itself and only have the ability to view and fill out different forms for the organization or customer they're added to. This means anyone added at a customer level will only have access to forms for that customer, while a user added at the top-level organization would have access to forms from any customer organization and the top-level organization itself.
Read Only
The Read Only Role has been introduced to meet various needs. The primary use case is to grant lower-level technicians access to Rewst, enabling them to view workflow results. Additionally, it serves as a mechanism to limit access to certain features and configurations. Users with the Read Only Role can access Rewst and review data and information but are restricted from creating or updating anything within the platform.
Last updated