Cross-Team Visibility
Understand how ScenIQ surfaces dependencies between teams while respecting access boundaries. See what blocks you across the organization.
Why Cross-Team Visibility?
In large organizations, work rarely stays within a single team. A task owned by the Design team might block the Engineering team. ScenIQ makes these inter-team relationships visible so you can identify bottlenecks before they become critical.
Cross-Team Dependency Graph
On the Team page, the Cross-Team Dependencies section renders your team's tasks alongside tasks from other teams that have dependency relationships with yours. The graph uses visual distinctions to make ownership clear:
| Visual | Meaning |
|---|---|
| Normal node | A task owned by your team. Fully visible with title, status, priority, and assignee information. |
| Dimmed/external node | A task from another team that has a dependency relationship with one of your tasks. Shows full details if you have graph access. |
| Locked node | A task from a team you don't have access to. Shows "Hidden Task" with a lock icon and "Restricted access" label. No task details are visible. |
| Orange dashed edge | Cross-team dependency. Animated to draw attention. |
| Gray solid edge | Internal dependency within your team. |
The One-Hop Wall
ScenIQ implements a one-hop visibility model for cross-team dependencies. This means:
- You can always see the direct task blocking yours, even if it belongs to another team (subject to access grants).
- You cannot see what blocks that task in turn, unless the upstream team has also granted you access.
- Locked nodes display a "Blocked by N hidden teams" count so you know there are upstream blockers without seeing their details.
Example
Suppose Team X blocks Team Y blocks your team. You can see Team Y's blocking task if they've granted you access. But you cannot see Team X's task unless Team X also grants you access — even though it transitively blocks you.
Partial Access
Access is granted per-team, not per-task. If Team Analytics grants you access, you can see all of Analytics' dependency-related tasks. If Team Marketing has not granted access, their tasks appear as locked nodes even if they have dependencies with accessible teams.
This creates a selective visibility model:
- Accessible teams: Full task details visible (title, status, priority, assignees).
- Inaccessible teams: "Hidden Task" placeholder with lock icon. Team name is also hidden.
Dependency Metrics
The Team page shows two key cross-team metrics:
- Blocking us — Number of external tasks that are blocking tasks owned by your team.
- We block — Number of tasks your team owns that are blocking other teams' tasks.
These metrics help you prioritize which cross-team relationships need attention.
External Teams
Below the dependency graph, the External Teams section lists all teams you are not a member of, along with their access status relative to your team:
- No access — You haven't requested access. A "Request Access" button is available.
- Pending — You've requested access and are waiting for approval.
- Granted — Access has been approved. A "View Graph" button lets you see their full dependency graph.
See Graph Access Control for the complete request/grant flow.
Viewing external graphs