docs/versioned_docs/version-3.0.0-LTS/tj-setup/workspaces.md
Workspaces are collaborative environments that enable teams to build, customize, and deploy applications, as well as manage data, workflows, and permissions. It helps you organize your organization's apps based on hierarchy or departments, making them easier to manage. For example, if your organization has departments, you can create separate workspaces for each to isolate apps or limit access to particular set of users or developers.
Workspace contains applications, data sources, users (admins, developers, or builders, end users), access and permission settings, and more. You can also set different login configurations for each workspace. You can have multiple workspaces within an instance.
Role required - Workspace Admin
To create a new workspace,
https://app.corp.com/<workspace-slug>)Role required - Workspace Admin
To edit a workspace,
https://app.corp.com/<workspace-slug>)To switch between the workspaces,
https://app.corp.com/<workspace-slug>)Role required - Super Admin
This feature is available only for self-hosted users, and only Super Admin can archive workspaces. A Super Admin is the user who has full access to all the Workspaces, Users, and Groups of an instance
To archive a workspace, at least one active workspace must exist in the instance.
Impact
To archive a workspace:
https://app.corp.com/instance-settings/all-workspaces)Role required - Super Admin
https://app.corp.com/instance-settings/all-workspaces)Admin user has access to all the permission at workspace level, while an end user can only view and use the released apps they are given access to and permissions can be configured for a builder.
| Permission | Admin | Builder | End User |
|---|---|---|---|
| App | ✅ | Configurable | ❌ |
| Data sources | ✅ | Configurable | ❌ |
| Folder | ✅ | Configurable | ❌ |
| Workspace constants/variables | ✅ | Configurable | ❌ |