Workspaces
- Synopsis
- Full Details
In briefA workspace groups workflows, properties, thresholds, resources, scripts and service requests, and a role can be scoped to it — which is what makes a workspace the unit that decides who can reach that content. Every organization has a system General workspace that cannot be changed or deleted. Frequencies, calendars and tags are global and belong to no workspace.
WhereAdministration › Permissions › Workspaces tab (/permissions/workspaces),
which needs Workspaces View. A workspace can also be created from the role editor's New
Workspace button.
When
- You want to separate content that different teams own, or that a role should be scoped to.
- An item seems to be missing — it may be in another workspace.
- You want to delete a workspace and need to know what stands in the way.
How
- Open the Workspaces tab and select New Workspace.
- Enter a Workspace Name and a Description, and save.
- Grant roles permissions in it from each role's Workspaces and Environments tabs.
- Assign content to it. The full walkthrough is Manage permissions.
- There is no per-user membership: access to a workspace's content comes from role grants.
- Roles Using and Objects on the list show the two counts that block a delete, so you can see whether a delete will be refused before you try.
- An edit sends only the fields you changed.
- A workspace cannot be named General in any capitalisation or padding.
- A delete is refused while any role still grants permissions in the workspace or any object is still assigned to it. Remove it from those roles and move or delete the objects first.
Task walkthrough: Manage permissions, on its Workspaces tab. 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.
Where workspaces are managed
Workspaces are on the Workspaces tab of the Permissions page, under Administration in
the navigation, beside Roles, Event Identities and z/OS User IDs. The tab needs Workspaces View. Old links
under /workspaces redirect to the same place, at /permissions/workspaces.
| Column | Shows |
|---|---|
| Name | The workspace. The header has a filter |
| Description | Its description |
| Roles Using | How many roles grant permissions in this workspace by name. A grant for All workspaces is not counted against each one |
| Objects | How many workflows, properties, thresholds, resources, scripts and service requests are in it |
| Updated | When it was last changed. Sortable |
If the counts cannot be read, the list says Roles and objects couldn't be counted and shows — in both columns.
New Workspace (needs Workspaces Create) opens an editor dialog over the list. Each row's ⋮
menu offers Edit and Delete, and double-clicking a row opens it. The General workspace,
and every workspace for someone without Workspaces Edit, opens read-only, and its menu says
View instead of Edit. Read-only, the dialog is titled View Workspace: its fields can't
be changed and aren't marked required, and it has no Save or Delete, only Close. The dialog is addressed by URL — /permissions/workspaces/new and
/permissions/workspaces/<id> — so links to a workspace and Back both work.
| In the dialog | Notes |
|---|---|
| Workspace Name | Required. See the rules below |
| Description | Required in the editor for a new workspace, and once you clear a stored one. A workspace saved earlier with no description can still be saved without one |
| Objects in this Workspace | On an existing workspace only: a table of its objects with Type, Name, Description, Last Updated and Updated By. Opening one takes you to it, asking first if you have unsaved changes |
An edit sends only the fields you changed, so saving cannot undo a change someone else made after you opened the dialog. Closing with unsaved changes asks first.
A workspace can also be created from the role editor's New Workspace button — see Roles and permissions.
Model
| Field | Notes |
|---|---|
| Workspace Name | Unique in your organization; 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 | Up to 500 characters. Required in the editor for a new workspace, as described above. |
| System workspace | The General workspace is a system workspace — it can't be changed or 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.)
An object shows its workspace by name to anyone who can view the object. The Workspace field in the editor of a workflow, script, service request, property, resource or threshold, and the Workspace column on the Scripts, Self Service, Properties, Resources and Thresholds lists, show the name of that object's own workspace, whether or not you hold Workspaces View. Choosing a different workspace still lists the workspaces from the Workspaces tab, which needs Workspaces View. When the name cannot be looked up, the workspace's ID is shown instead. A renamed workspace shows its new name on the lists within about a minute. Earlier builds showed the ID to anyone without Workspaces View.
Membership
There is no per-user workspace membership today. Access to a workspace's content is governed by role grants (a role can grant permissions in a workspace), not by adding users to a workspace — see Roles and permissions.
Deleting a workspace
A workspace is deleted only when nothing uses it. The checks run in this order:
| Refused when | What the refusal says |
|---|---|
| It is the General workspace | System-managed workspaces cannot be deleted |
| A role still grants permissions in it | Cannot delete workspace '…': 2 roles still grant permissions in it. Remove it from those roles first. |
| Objects are still assigned to it | Cannot delete workspace '…': 3 objects still assigned (workflows: 2, properties: 1). Reassign or delete them first. |
Roles Using and Objects on the list show the same two counts, so you can see whether a delete will be refused before you try. To clear the first, open each role that grants in the workspace and remove the workspace from its Workspaces and Environments tabs.
- "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, a role still grants in it, or it still has objects | Remove it from the roles that grant in it, then move or delete its objects; the General workspace can't be deleted (Administrator). |
| A user can't see content you expect | None of their roles grants that permission in that workspace — see Where a grant applies | Check the role's Workspaces and Environments tabs (Administrator). |