Workspaces
Task walkthrough: Manage workspaces. This page is the full configuration and troubleshooting reference.
A workspace groups and isolates content. Every tenant gets a system General workspace automatically. Administrators create additional workspaces to separate content that different teams own, or that a role should be scoped to — because a role can be scoped to a workspace, a workspace is the unit that decides who can reach a set of workflows, properties, thresholds, resources, scripts, and service requests.
Model
| Field | Notes |
|---|---|
name | Unique per tenant; cannot be "General" (reserved). The reservation is matched without regard to case or padding, so general, GENERAL and " General " are all refused too. 3–255 characters, and it may not be blank or padded with whitespace — see Object naming. |
description | Optional, up to 500 characters. |
isSystem | The General workspace is a system workspace — immutable and can't be deleted. |
What's scoped to a workspace
Workflows, properties, thresholds, resources, scripts, and service requests. (Frequencies, calendars, and tags are global, not workspace-scoped — see Toolkit overview.)
Membership
There is no per-user workspace membership today. Access to a workspace's content is governed by role scopes (a role can be scoped to a workspace), not by adding users to a workspace — see Roles and permissions.
- A workspace can't be deleted while it still contains objects — the error lists what's left (e.g. "2 workflows, 1 property") and they must be reassigned or deleted first. System workspaces can never be deleted.
- "Missing" workspace-scoped items (a property/threshold/resource/script) are usually in a different workspace — confirm the workspace before treating it as lost.
Troubleshooting
| Symptom | Likely cause | Resolution |
|---|---|---|
| Can't delete a workspace | It's the system workspace, or it still has objects | Move/delete its objects first; the General workspace can't be deleted (Administrator). |
| A user can't see content you expect | Their role scope doesn't cover that workspace (note: enforcement caveat in roles doc) | Check role scopes (Administrator). |