Overview
Manifest provides a robust system of user roles to manage access and permissions effectively. The roles available to assign depend on the type of license associated with your organization and assigned to each user. Each role is tailored to specific functions, controlling what users can view and perform within the platform.
Key Features of User Roles
- Role-Based Access Control: Every role comes with predefined permissions that align with typical responsibilities, ensuring users have the access they need—and nothing more.
- Flexible Role Assignment: Users can hold multiple roles, enabling businesses to customize access and functionalities to meet their unique operational needs.
- Enhanced Security and Efficiency: Tailored permissions help maintain security and streamline workflows by ensuring users only interact with relevant features and data.
Benefits of Customizable Permissions
- Improved Operational Control: Assigning roles based on responsibilities ensures clear boundaries and accountability.
- Scalability: As your needs evolve, roles can be adjusted to accommodate new users, processes, or operational changes.
For detailed information about License Types and the specific User Role Permissions available in Manifest, refer to the sections below.
License Types
License Types Overview
Manifest offers three distinct license types, each tailored to specific user needs and roles within your organization.
| Full License | The comprehensive license designed for administrators and power users. This license enables users to create, manage, and operate Manifest work instructions, offering complete control over the platform’s functionality. |
| Operate License | Tailored for frontline workers, this license focuses on executing Manifest work instructions and facilitating real-time collaboration with remote experts. |
| Connect License | A lightweight license ideal for users who need to view Manifest work instructions, access operational data, and engage in remote collaboration. |
User Roles Available by License Type
Each Manifest license type includes the option of enabling a predefined set of user roles. User Administrators are responsible for assigning the appropriate license type 1) depending on what is available for your domain or Org and 2) what is appropriate for the specific user.
| User Role | Full | Operate | Connect |
|---|---|---|---|
| User Admin |  | |  |
| Admin | | | |
| Security Admin | | | |
| Operator | | | |
| Viewer | | | |
| Author | | | |
| Approver | | | |
| Publisher | | | |
User Roles and Permissions
User Roles Overview
| User Role | Access Type | Access Overview | Notes |
|---|---|---|---|
| User Admin | User & License Management | Responsible for provisioning users in your Manifest instance or their assigned organization. | Available on web application only. Only users with this role can add or edit users. |
| Admin | Setup & Configuration | Oversees the setup and configuration of Manifest, including organizational structures and company-wide settings. | Admins at the root level can access Client Settings to customize the Company Profile, Welcome Messages, and EULA. |
| Security Admin | Security Management | Ensures the security of Manifest but does not have access to view or modify operational data. | Available on web application only. Security Admins at the root level can configure 2FA and Password requirements for the domain. |
| Operator | Operate | Handles day-to-day operations like Jobs, Tasks, and Fault resolution. | Known as the “doers” in the system. |
| Viewer | View Only | Provides ‘view only’ access to Manifest content and full access to Manifest Connect. | Ideal for stakeholders or auditors who only need to review information. |
| Author | Content Creation & Management | Creates and manages content to power Manifest, including Templates, Assets, and Asset Classes. | Ensure subject matter experts and content curators are assigned this role. |
| Approver | Editorial – Approver | Reviews and approves Templates to ensure they meet quality and safety requirements. | If your team doesn’t require reviews, assign Approver and Publisher roles to all Authors. |
| Publisher | Editorial – Publisher | Publishes approved Templates and ensures only authorized procedures are available to users. | If your team doesn’t require reviews, assign Approver and Publisher roles to all Authors. |
User Role Permissions Grid
| Type | Permission | User Admin | Admin | Security Admin | Operator | Viewer | Author | Approver | Publisher |
|---|---|---|---|---|---|---|---|---|---|
| User Mgmt | Add/Edit Users | | | | | | | | |
| User Mgmt | View and Provision Licenses | | | | | | | | |
| User Mgmt | Assign User Roles | | | | | | | | |
| User Mgmt | Assign Org Access to Users | | | | | | | | |
| User Mgmt | Manually Set Passwords | | | | | | | | |
| Administrative / Setup | Add/Edit Orgs | | | | | | | | |
| Administrative / Setup | Assign Asset Classes to Orgs | | | | | | | | |
| Administrative / Setup | Add/Edit Assets | | | | | | | | |
| Administrative / Setup | Enable/Edit Welcome Message* | | | | | | | | |
| Administrative / Setup | Enable/Edit Enterprise EULA* | | | | | | | | |
| Security | View User Logs | | | | | | | | |
| Security | Set Password and Session Requirements* | | | | | | | | |
| Security | Enable Two-Factor Authentication* | | | | | | | | |
| Security | Enable/Configure Domain SSO | | | | | | | | |
| Operate | Add Jobs & Tasks | | | | | | | | |
| Operate | Assign/Reassign Jobs and Tasks | | | | | | | | |
| Operate | Cancel Jobs & Tasks | | | | | | | | |
| Operate | Add/Resolve Fault | | | | | | | | |
| Operate | Take Work Offline | | | | | | | | |
| View | View Asset Classes & Assets | | | | | | | | |
| View | View Templates | | | | | | | | |
| View | View Jobs, Tasks, and Faults | | | | | | | | |
| Create/Modify Entities | Add/Edit Asset Classes | | | | | | | | |
| Create/Modify Entities | Add/Setup Asset Class Models, Documents, Meters | | | | | | | | |
| Create/Modify Entities | Add/Edit Templates | | | | | | | | |
| Create/Modify Entities | Import Manifest Package* | | | | | | | | |
| Editorial | Approve/Reject Templates | | | | | | | | |
| Editorial | Publish Templates | | | | | | | | |
| Editorial | Archive/Unarchive Templates | | | | | | | | |
| Connect | Chat with users | | | | | | | | |
| Connect | Call users (Video/Audio) | | | | | | | | |
| Connect | Direct user | | | | | | | | |
| Connect | Create a group chat | | | | | | | | |
| Connect | Share Work or Files | | | | | | | | |
Understanding the Asterisk (*)
Permissions marked with an asterisk (*) indicate which permissions are restricted to users assigned to the Root-level Org, which represents the highest level of the organizational hierarchy. This indictoar is only relevent if Orgs are enabled for your domain. If you are operating within an Org below the Root level, the asterisked permissions will not apply to those user roles.
If Orgs are not enabled for your domain, you can disregard the asterisk. Those permissions will apply to any user with that role.
