Keep data work scoped to each team

Team scoping ties every resource in SyneHQ to the team that created it. When a user switches teams, the connections, queries, dashboards, notebooks, watchers, and workflows they see change to match. The check happens before the request proceeds, not after.

How it works

Each session carries the active team. When a request touches a resource -- opening a connection, loading a dashboard, running a saved query -- the platform confirms the resource belongs to the active team before the operation continues. A mismatch stops the request. There is no cross-team resource list and no ambient access to another team's work.

What is scoped

Connections are owned by the team that created them. Saved queries belong to the connection they were written against, and that connection belongs to a team. Dashboards, notebooks, watchers, and workflows follow the same rule: each one is tied to the team that owns it, and only members of that team see it in their workspace.

Relationship to other controls

Team scoping governs which resources are visible inside SyneHQ. It does not extend to the databases themselves. Row-level security, network access controls, and credential management remain the responsibility of the database operator. Team scoping and those external controls work in parallel -- team scoping limits what appears in the interface, while database-level controls limit what the connection can reach.