Keep resources together.
Connections, queries, notebooks, and dashboards belong to their team’s workspace.
A home for the team’s work
Shared work with clear team boundaries
One place to work.
A clear space for each team.
Keep connections, queries, notebooks, and dashboards in the team that owns them. Switch workspaces without mixing one team’s resources into another.
Connections, queries, notebooks, and dashboards scoped to your team.
Team scoping works alongside your database permissions and network controls.
A closer look at Team Scoping.
Product preview · Sample dataWhy Team Scoping
Shared data work within team boundaries.
Switch teams with context.
Move into another team and see the resources that belong to that active workspace.
Separate working contexts
Check access on the request.
Resource ownership is checked against the active team before access proceeds.
Enforced beyond the interface
Keep shared work in the right workspace
Your active team determines which resources you can open. Connections belong to a team; saved queries belong to those connections. Notebooks, dashboards, watchers, and workflows follow the same ownership boundary.
The check happens on the request, so resource access stays scoped beyond the interface. Database permissions still determine what each connection is allowed to do.
What changes when I switch teams?
The resources you can access change to the active team: connections, queries, notebooks, dashboards, watchers, and workflows.
Is this only a filter in the interface?
No. Resource access is checked against the active team on the request. A resource belonging to another team cannot be opened through that request.
Does this replace database permissions?
No. Database privileges, row-level security, credentials, and network controls still govern what a connection can reach. Team scoping governs resources inside SyneHQ.
Bring the team together around its own data.
Keep shared analysis and operations in the workspace that owns them.