Organizations & workspaces
Pradra Studio is built for teams. Two containers keep work organized, isolated, and safe.
The two containers
- An Organization is your top-level tenant — your company or business unit. It owns everything: users, workspaces, subscriptions, budgets, and governance. Data never crosses an organization boundary, structurally.
- A Workspace is a collaboration and isolation boundary inside an organization. Solutions, datasets, capabilities, and members live in a workspace. Teams use separate workspaces to keep their work — and their data — cleanly apart.
An organization can have many workspaces. You switch between the ones you have access to with the context switcher in the top bar — everything you see and create is scoped to the selected workspace.
Getting an organization
- Self-serve registration: sign up from the login screen and you get a new organization with you as its administrator and a default workspace, ready to use.
- Invitation: an administrator adds you to an existing organization and assigns your workspaces and role.
Lifecycles
| Container | Lifecycle |
|---|---|
| Organization | Provisioned → Active → Suspended → Deleted |
| Workspace | Active → Archived → Deleted |
Archiving a workspace when a project ends is reversible — the work comes back exactly as it was if the project does. Deletion is the deliberate, confirmed end.
Working with them in the Studio
- Administration in the sidebar is home for organization and workspace management (administrator roles required).
- Create workspaces per team or per initiative — a workspace is cheap; a tangled shared one is not.
- Members are added per workspace with a role that sets what they can do there.
- Organization-level concerns — secrets, budgets, subscription, fine-tuning consents — have their own pages, all scoped to the current organization.
What isolation buys you
- A workspace member sees only the workspaces they belong to; data from one workspace is never visible from another.
- Cross-tenant references simply do not resolve — asking for another organization's resource answers "not found", never "forbidden but it exists".
- Every capability, dataset, and knowledge source is workspace-scoped, so an agent or a retrieval query can never reach across the boundary either.
Next
- Who can do what: Users & roles.