Skip to main content
Governance maps people to parts of the schema. It defines who owns specific types and subgraphs, and it enforces review before changes reach production.
Governance doesn’t restrict editing on branches. It controls approval at the proposal stage.

​
Three roles

Graph admins have full control. They can approve any proposal and manage governance settings. Type owners own specific types. They review any change that modifies their type, regardless of which subgraph resolves it. Subgraph owners own specific services. They review any change that assigns, removes, or modifies fields in their subgraph. Type ownership and subgraph ownership are separate. A single change can require approval from both.

​
How enforcement works

Governance activates when you create a proposal:
  1. Hub analyzes the schema changes.
  2. It identifies affected types and subgraphs.
  3. It assigns their owners as required reviewers.
  4. The proposal stays blocked until every required reviewer approves.
  5. Unresolved discussion threads also block approval.
No one can skip a required review. If an owner hasn’t approved, the proposal doesn’t merge — regardless of check status.

​
Set it up early

Assign type owners for shared entities. Assign subgraph owners for every service. Keep graph admin access limited to platform leads. Clear ownership means proposals route to the right people from the start.
See Assign Ownership for the setup walkthrough.

​
Limits

Governance doesn’t restrict branch edits, assign implementation work, or apply across graphs. It requires proposals to enforce review, and it assigns all affected owners as required reviewers — there’s no partial approval.