Team Workspace

A guide to Data Explorer collaboration: organization structure, teamspaces, resource sharing, comment threads, activity feeds, and team-level backup/restore.

Organization and member roles

Each team works inside its own organization with a member list, invitations, roles, and context-aware resource access.

Teamspaces and resource groups

Connections, saved queries, and dashboards are not just shared or private; they can also be grouped into teamspaces for a cleaner working structure.

Comments and activity

Resources can carry comment threads and activity history so the whole team can understand who is using, editing, or watching a data asset.

The collaboration structure inside the app

TeamPage acts as a coordination surface for multiple concepts at once: organizations, members, teamspaces, shared resources, activity, and backup. That means the Team Workspace docs are useful not only for admins, but for anyone who needs to understand how resources grow from personal to team scope.

Organization

This is the outer container for members, invitations, resource policies, and backup/export. If you think in terms of a company or team-level workspace, this is the right unit.

Teamspace

This is the subgroup inside an organization that helps cluster resources by product, domain, customer, or runtime environment.

How resource permissions work

Readable permission labels

In the UI, resources are summarized into readable levels such as read, comments, edit, or manage instead of exposing raw policy definitions.

Comment is not the same as edit

A user may be allowed to comment on a resource without being allowed to edit it. That distinction matters for review workflows.

The resource types currently managed

Right now the Team Workspace is centered on the three most important shared asset types: team connections, shared queries, and team dashboards. Those are the places where data knowledge most easily gets trapped in personal silos, so the app governs them together.

Comment threads, activity feeds, and collaboration history

Resource-specific comment drawer

Comments open in the context of a specific resource rather than a generic chat box. That keeps the conversation attached to the exact connection, query, or dashboard under review.

Activity tab for the bigger picture

If the comment drawer is the local view for one resource, the activity tab is the organization-wide view: who changed what, where, and what the recent work stream is orbiting around.

Team-level backup and restore

TeamPage includes a dedicated backup flow that exports an organization package as JSON and restores it in a controlled way. It is useful for light migration, collaboration-config backup, or creating a snapshot before major changes.

When to export a backup

Export before broad changes such as teamspace restructuring, share-policy updates, moving resources between groups, or collaboration cleanup. It does not replace full database backups, but it is extremely useful for organization-level metadata and collaboration state.

Moving data between two connections (Migration)

The migration tool streams data from a table/collection on a source connection to a target on another connection — even across engine types (e.g. MySQL to PostgreSQL).

Pick source and target

Select the source connection, database/schema, and table; then pick the target connection and receiving table. The system blocks source and target pointing at the same table.

Verify schema compatibility

A preflight compares the columns of both tables and fails when the target is missing required columns. Create the target schema first (via SQL Steps or the schema editor) if it does not exist yet.

Run and watch progress

The transfer runs in adaptive batches inside a background job: you see processed rows, batch count, and the current stage (validating → connecting → preflight → streaming → completed).

Handling mid-run failures

If the source or target connection drops, the job fails and stops at the current batch — no partial writes because each batch is committed in a transaction. Fix the issue and rerun from the start.

Treat Team Workspace as the governance layer for data assets, not just a place to casually invite teammates. Sharing a connection, commenting on a dashboard, or widening a policy all have real consequences for how the team works with data.

PreviousInteractive Charts Next Authentication & Onboarding

Ready to explore data?

Join the community on GitHub to contribute to the smartest local database IDE.

Launch App