1
Organisation versus workspace
The organisation is the customer, identity and membership boundary. A workspace is an isolated operational environment with its own tickets, assets, endpoint agents, queues, teams, policies and reporting.
- Use one workspace for a shared operating model.
- Use multiple workspaces for genuinely separate teams, customers, regions or policy boundaries.
- Do not create workspaces merely as folders; separation changes operational context.
2
Switch active workspace
Use the top-bar selector to choose the current workspace. Ordantra stores the selection and validates it against organisation membership on every request.
- All operational screens follow the selected workspace.
- Invalid, archived or cross-organisation selections are ignored.
- Organisation members can switch; lifecycle management requires Owner or Admin.
3
Create and name workspaces
Owners and admins can create and rename workspaces from the Workspaces page. Choose names that make the operational boundary obvious to every resolver.
- Keep the default workspace for the primary operation.
- Review queues, teams, SLA, automation and agent enrolment after creating a workspace.
- Remember that new workspaces begin empty by design.
4
Archive and restore
Archiving removes a workspace from live operational selection without deleting its history. The final active workspace cannot be archived.
- Switch active work away before archiving.
- Archived workspaces retain lifecycle audit records.
- Restore when the operation needs to become active again.