For the complete documentation index, see llms.txt. This page is also available as Markdown.
Workspaces overview
Understand the top-level boundary for people, projects, data, models, and releases.
A workspace is the top-level operational boundary in Unitlab. It contains members, roles, projects, Data Space, datasets, ontologies, models, releases, storage configuration, and subscription or quota context.
Use this area when: you are creating an environment, separating organizations or programs, managing shared resources, or governing access and capacity.
How this area fits into production
Workspace switcher open from the Unitlab sidebar
The workspace switcher is the boundary selector for projects, Data Space, datasets, models, members, releases, and settings. The item count beside each workspace helps confirm context before entry; New Workspace starts a separate boundary.
What this area controls
The workspace area includes:
workspace list and switcher;
general settings for name, purpose, and logo;
account security and 2FA;
billing and pricing portal;
usage and quota visibility;
members and member statistics;
Roles & Permissions editor;
API keys;
cloud storage connections;
user profile.
Usage can report datasource, image, video, medical, token, audio-duration, AI-inference, and member consumption. The interface warns when a downgraded plan would be exceeded.
Workspace destruction is intentionally different from leaving a workspace. It is Owner-only, requires the exact workspace name, and requires a second factor when the Owner has 2FA.
Start with the right page
Decision
Production guidance
Create or enter a workspace
Use workspace creation and switching.
Manage shared configuration
Use workspace settings.
Control people
Use members, roles, and permission groups.
Control source connections
Use storage and cloud settings.
Plan capacity
Review quotas, subscription, and operational limits.
Review governance
Run periodic workspace operations and access review.
Operating boundary
Use separate workspaces when identity, ownership, data policy, or administrative control must be isolated.
Project permissions do not replace workspace governance.
Workspace settings changes can affect every project and integration in the boundary.
A production-ready handoff
The workspace has accountable owners, a defined purpose, approved membership, resource naming standards, shared configuration ownership, capacity monitoring, and an offboarding process.
