DocsTeamsGraph Access

Graph Access Control

Control who can see your team's dependency graph. Request access to other teams' graphs and manage incoming requests.

How Graph Access Works

By default, a team's dependency graph is only visible to its own members. To see another team's graph, you must request access, and an admin on that team must grant it.

Access grants are one-directional: if Team A grants access to Team B, Team B can see Team A's graph, but Team A cannot automatically see Team B's graph unless Team B also grants access in return.

Access States

StateDescriptionAvailable Actions
NoneNo access request has been made.Request Access
PendingRequest submitted, awaiting admin approval.Wait (or contact the admin directly)
GrantedAccess approved. Full graph visibility enabled.View Graph

Requesting Access

1

Navigate to the Team page

Click Team in the sidebar and select your team.

2

Scroll to External Teams

The External Teams section lists all teams you are not a member of, along with their current access status.

3

Click "Request Access"

On the team you want to view, click the "Request Access" button. The status changes to Pending immediately.

4

Wait for approval

An admin on the target team will review and approve (or deny) your request. Once granted, the status updates to Granted and a "View Graph" button appears.

Granting Access

When another team requests access to your graph, team admins can approve the request. Currently, access grants are managed through the admin interface.

Admin-only action

Only team admins can grant or revoke graph access. Regular members can request access but cannot approve incoming requests.

What Access Grants Reveal

When access is granted, the requesting team can:

  • View the full dependency graph of the granting team, including task titles, statuses, priorities, and assignees.
  • See cross-team dependencies from the granting team to your team (and vice versa) with full context instead of locked nodes.
  • View the granting team's dependency graph via the "View Graph" button in the External Teams list.

Importantly, access does not grant the ability to edit, create, or delete tasks — it is read-only access to the dependency graph.

Transitive Visibility

Access grants do not cascade. If Team A grants access to Team B, and Team B grants access to Team C, Team C cannot see Team A's graph through Team B. Each team must explicitly grant access to each viewer.

This design ensures that sensitive project information stays within controlled boundaries. See Cross-Team Visibility for how the one-hop wall model works with these access grants.

Best practice

If two teams frequently collaborate and have cross-team dependencies, consider establishing mutual access — both teams grant access to each other. This provides the clearest picture of shared blockers.

Revoking Access

Team admins can revoke previously granted access at any time. Once revoked, the viewer team's access is immediately removed, and their graph views will show locked nodes for your team's tasks.