Compliance programs often contain sensitive information that must be restricted to specific teams or individuals. For example, a manager of a security program may not be allowed to view a privacy program.
Object roles and permissions define how users interact with specific objects such as compliance programs, controls, audits, and related data. Roles determine whether users can manage, contribute to, or view an object.
Object roles and permissions are assigned when a user is added to an object or their role needs to be updated to reflect their responsibilities. These assignments should be reviewed and adjusted to align with changing roles or organizational needs.
To participate in an object—programs, controls, labels, proof, audits, risks, or vendors—members of an organization (except administrators) must be explicitly added to it and given a specific level of access.
Defining object roles
Hyperproof has the following object-level roles:
Manager: A manager manages a particular object and its members. Managers can perform nearly every function within the object they manage.
Contributor: A contributor performs certain activities in an object they’ve been added to, such as linking, importing, and exporting.
Viewer: A Viewer can see files and information about particular objects where they are a member.
Important: Users, whether managers, contributors, or viewers, must be added to an object before they can interact with it. Administrators can change their roles on an object at any time.
We recommend you navigate to the help center document using the link below and bookmark it for future reference. This help center section provides detailed information on the actions within Hyperproof that each role can take based on their object-level permissions.
Permissions by role
To learn more about permissions by role, we recommend you visit our help center or search for roles and permissions in Hyperproof.