Skip to main content

Control Access with Ownership Blocks

This guide explains how Ownership Blocks dynamically grant or restrict permissions within collaborative documents. When used with project roles, Ownership Blocks enable precise access control for editing, commenting, and approval actions.

These rules are enforced automatically based on who is assigned to the block in a live project.

When to Use Ownership-Based Access​

You should use Ownership-Based access when you want to:

  • Allow users to edit only specific content in a shared document.
  • Prevent users from modifying sections they don’t own.
  • Define review or approval steps based on content ownership.

How Access is Granted​

When a user is assigned to a project role that owns a block:

  • They automatically receive permission to edit, comment, or approve that specific section.
  • Their permissions apply only to the content governed by the block.
  • Even if their overall project role is more restricted, the block gives them elevated rights for that section.

How Access is Restricted​

If a user is not assigned to a block:

  • Their access to that content may be limited or read-only, even if they have broad permissions elsewhere.
  • This ensures users don’t unintentionally modify sections outside their responsibility.
Note

In live projects, Ownership Block permissions are enforced automatically. Review related workflows and role assignments before editing templates.

See Also​

To complement your knowledge, check the following guides: