Workspaces
Workspaces group related database work into a named project context. Use them to separate client projects, local experiments, staging systems, and production operations.
What belongs in a workspace
A workspace can hold:
- database connections
- query files and folders
- recent activity context
- environment tag usage
- workspace-specific visual identity such as name and icon
Recommended setup
Create separate workspaces for meaningfully different scopes:
- one workspace per product or client
- one workspace for local development databases
- one workspace for production operations
- temporary workspaces for migrations or incident response
This keeps connection lists short and reduces the chance of running a query against the wrong environment.
Safety notes
Pair workspaces with Environment Tags so production-like connections are visibly marked and protected by strict mode.