Note: This article covers Personas which were introduced as of our most recent update (R28+). If you are looking for similar information about our legacy experience (R27), please refer to this article.
Personas drive access to an app within a tenant with specific permissions. They also align 1-for-1 to license types, except for the 'Analytics Dashboard' license type. For example, a user assigned the Reader persona uses a Read-Only User license. A user assigned a Member persona uses a Standard User license. Administrators can adjust their organization's license allocations by updating a user's assigned personas.
The possible personas for the Core Platform app include:
- Member users are those with write access to the system. Can be internal or external users.
- Reader users are those with read-only access to the system. Can be internal or external users.
- Agency users are external users who can view and initiate documents, based on the permissions and configurations set up in your system.
The possible personas for the Admin app include:
- Administrator users have access to the Admin Console, where they can view and manage users, invite new users, and configure other system settings to meet the needs of your team.
The possible personas for the Portals app include:
- Member users are those access to the system.
Users are assigned a persona during initial setup, which can be updated later. Each user may have only one persona per application. Personas can be configured to require specific non-removable ("required") permissions (i.e., groups) or limit the available groups that can be assigned ("optional") to a user.
| Persona | Description | Notable Details | Example Users |
|---|---|---|---|
| Administrator | Provides access to the Admin Console which gives the user permission to perform Vodori user management across the organization | Users who require access to both the Admin Console and the Core Platform should be assigned a persona in both apps | System Owner, IT Manager |
| [Core Platform] Member | Can perform any action in the Core platform that their configured permissions allow. | The only restrictions are driven by customer configuration | System Owner, Marketing, Regulatory, Medical, Legal, Other Reviewers |
| Reader | Can view and may be permitted to download any content within the system to which they have been granted access | Cannot start a workflow, upload content, comment on a document or perform review task | Quality, Marketing team members that do not create content, Executives |
| Agency | Intended for creative agencies to allow them to upload content and substantiate claims |
Cannot perform review tasks and cannot view content they are not designated to view.
|
Creative/marketing agency partners |
| [Portals] Member | Can view content in the Portals app according to their configured permissions | The ability to create Collections is an available extended permission | Sales, Distributors |
⚠️ If you are looking for information user types in our legacy experience (R27), please refer to this article.
Comments
0 comments
Please sign in to leave a comment.