Skip to main content

Inherited permissions

Learn how inherited permissions work in a Hyperproof object.

Danielle Moerman avatar
Written by Danielle Moerman
Updated over 5 months ago

Note: The information below is shown for an administrator role. If you have another role in Hyperproof, like compliance manager, user, or limited access user, your access may be limited due to your organizational role and object-level permissions. We recommend viewing the organization roles and permissions article and object roles article to learn more about permissions.

It’s important to note that some users may inherit permissions within an object. This means a user who creates an object inherits some permissions to access additional objects created within the original object.

Example of Inherited permissions in Hyperproof:

Luna works in IT and is responsible for linking proof to 10 controls within her organization. Since she only links proof and doesn't need access to everything in her organization, she holds the role of User-Proof Creator, where the user refers to the organizational tier and the proof creator refers to the object tier.

In the example above, Luna's role is that of a user-proof creator. Due to the way Hyperproof handles roles and permissions, Luna inherits the following additional roles and permissions:

  • Program manager

  • Program contributor

  • Control manager

  • Control contributor

  • Label manager

  • Label contributor

Check out our article on the help center to learn more:

Did this answer your question?