Understand Ownership Block Overrides and Hierarchies

This article explains how Ownership Block permissions interact with broader project role permissions. It also covers which users can override these restrictions.

How Ownership Blocks Relate to Project Roles

Ownership Block permissions are:

• More granular than general project role permissions.
• Enforced specifically for the content they govern.
• Applied dynamically based on role or user assignment.

For example:

• A user with read-only access in the overall project may still be allowed to edit a section if they own that block.
• Conversely, a user with broad edit rights may be restricted from editing a section they don’t own.

Who Can Override Ownership Blocks

The following users can override Ownership Block restrictions:

• Project Owners: Can view and edit all content, regardless of ownership.
• Administrators: Always have full access, even for restricted sections.

Note

While Ownership Blocks provide strong content-level control, administrative roles are not limited by them.

Best Practices

• Use Ownership Blocks for structured collaboration, not to enforce strict security.
• Avoid relying on overrides unless necessary for project maintenance.

See Also

To complement your knowledge, check the following guides:

• Create Ownership Blocks in a Project Template
• Assign Owners to Ownership Blocks
• Configure the Scope of an Ownership Block
• Modify Ownership Blocks: Update Assignments and Adjust Scope
• Control Access with Ownership Blocks
• Troubleshooting Access Issues with Ownership Blocks