Skip to Content

Workspaces

Group a team's applications, groups, APIs, policies and roles under named people who manage them and grant access.

Requiresworkspaces

Plan note: Workspaces are available on the Advanced and Pro plans, and in the trial with one workspace. See License and downgrade for what happens when a license no longer includes them.

Beta: Workspaces are new in this release and marked Beta in the console. Details of the feature may still change in upcoming releases.

A workspace groups related resources (applications, groups, APIs, authentication policies and roles) and puts named people in charge of them. Use workspaces to hand a team responsibility for its own resources without giving them access across the whole instance, and to make sure that only the right people can grant access to a workspace's applications.

Concept

A workspace has two kinds of people:

  • Responsibles: the workspace leads. They manage the workspace's members and settings.
  • Members: the people who do the day-to-day work, each with one or more permissions scoped to the workspace's resources.

A resource belongs to at most one workspace. Adding an application, group, API, policy or role that already belongs to another workspace is rejected.

Member permissions:

PermissionLets the member…
Manage resourcesmanage the workspace's applications, APIs and authentication policies, and create and manage its groups (including their membership) and roles (including their assignments)
Manage accessgrant and revoke access to the workspace's applications

Inside the workspace, these permissions apply regardless of the member's admin console access level. Any admin console user can be added as a member, and the responsibles decide what they may do there: a Viewer with Manage resources manages the workspace's groups and roles, a Support admin with Manage access also assigns the workspace's applications to employees, groups and workforce directories. Outside the workspace nothing changes: the access level alone decides, so a Viewer still only reads the dashboard and Support still only manages external users.

Roles follow the same boundary: a member can only attach roles of workspaces in which they hold Manage resources to a group or application, so a role from outside cannot be handed out through a workspace group or application. Admins whose access level manages roles or groups instance-wide (Operator and above) are not restricted this way.

Managing access with a workspace

By default, adding resources to a workspace only organizes them. Turn on Workspace members manage access in the workspace's settings to protect them: while it is on, only workspace members with the matching permission (plus the workspace's responsibles and full administrators) can

  • assign or revoke the workspace's applications (application assignment),
  • change the membership of the workspace's groups, directly or by adding a user to such a group (group membership),
  • assign or revoke the workspace's roles, to users or by attaching them to a group (role assignment), and
  • edit or delete the workspace's groups, including the directory group a group is linked to (group edits).

This also applies to the groups and roles set when an administrator creates a user.

This closes a common gap: without it, someone who cannot assign an application directly could still grant access to it by adding a user to a group that already has the application. Full administrators are never locked out, and directory synchronization continues to update synced groups.

Management API: a management API client acts without a personal identity, so it cannot hold a workspace permission. Its requests to make any of these changes on a workspace with managed access, or on an archived workspace, are always denied. Make such changes in the console, or keep the resources in a workspace without managed access.

Containment: while managed access is on, the workspace's applications can only be assigned to groups of the same workspace, and not to directories at all, because the membership of a group from outside or of a directory is not protected by the workspace. Assignments that already existed keep working and are marked Outside workspace on the application's Access tab; move the group into the workspace or revoke the assignment. Organizations are different: approving an application for an organization is itself an access decision, so it requires Manage access (or a responsible or full administrator). Within that approved set, the organization's administrators then authorize their members themselves; while the workspace is archived, they cannot. The same applies to the workspace's roles: while managed access is on, a role of the workspace can only be attached to groups of the same workspace. Revoking is always possible.

How to

Create a workspace

  1. Go to Governance → Workspaces and select Create workspace.
  2. Give it a name and an optional description.
  3. Open the workspace and add responsibles, members and resources.

Creating and deleting workspaces, and appointing responsibles, is reserved for full administrators.

Add responsibles and members

  1. On the workspace's People tab, use Add responsibles (administrators only) to appoint workspace leads.
  2. On the same tab, use Add members to add people and tick the permissions they start with right in the same dialog. A single member's permissions can be changed later with the edit button in the member list.

Add resources

On the Resources tab, add applications, groups, APIs, authentication policies and roles. Only resources that do not already belong to another workspace can be added. Each picker lists up to 500 resources per type; if there are more, search by name to narrow the list. Adding and removing existing resources is reserved for full administrators, so a responsible cannot extend their own reach by pulling in resources. New resources are created the usual way (for example under Applications → Create) with the workspace picked in the create dialog; the resource then belongs to it immediately. Groups and roles can be created by any member with Manage resources; new applications (including catalog integrations), APIs and authentication policies only by the workspace's responsibles and full administrators, so the responsibles decide what the workspace contains. Initial access tokens for dynamic client registration, which let applications register themselves outside any workspace, are reserved to full administrators.

Turn on managed access

Open Actions → Settings on the workspace page and enable Workspace members manage access. From then on the workspace's applications and group memberships are governed by the permissions above.

Reference

The workspace page is organized in tabs: Overview (bindings, certification status and recent activity), People (responsibles and members), Resources (all resources of the workspace), Access (the access review) and Audit logs, which lists every workspace change (created, updated, members and resources added or removed), every blocked access attempt, and the access changes on the workspace's resources (application assignments, group memberships, role assignments).

The Audit logs tab and the activity widgets show audit log entries, so they are only visible to admins whose access level may read audit logs (not to the Viewer level). The Access tab lists users, so it is likewise hidden from the Viewer level. Auditors can open every workspace read-only; they cannot change settings or members, export, archive or sunset.

The overview ends with the Baseline: a fixed set of checks that describes what a well-governed workspace looks like, limited to what the workspace's responsibles and members can fix themselves. It shows how many checks are met and, for each open one, what is missing and where to fix it:

  • every application enforces MFA for every login,
  • every application is covered by an access certification, and the reviews are up to date,
  • access is only held through the workspace, no dormant, inactive or locked account holds access, and access a certification revoked is gone,
  • access is mostly granted through groups (a warning when direct assignments make up more than a fifth),
  • there are at least two responsibles,
  • provisioning is active for the applications that offer it, and
  • Workspace members manage access is on.

Checks that do not apply (for example certification without the workflows feature) are not counted. The access checks look at the same list as the Access tab: when that list is longer than the entries scanned, a check without findings is shown as not fully checked instead of met. Instance-wide settings such as password rules or threat protection are covered by Security health, not here.

The overview also shows, where the features are available:

  • Bindings: a table with one row per application of the workspace, showing what each one is wired to: its authentication requirement, the workflows for access requests and certification, and how many of the workspace's APIs, groups and roles are connected to it. A dash means nothing is bound, which makes gaps easy to spot. Only resources of this workspace are counted; groups and roles from outside can still grant access to these applications.
  • Access certification: the latest review campaign per application, with status, progress and due date.

The Access tab lists every employee (workforce user) with effective access to the workspace's applications; external users are not listed, the same as in access certification. For each entry it shows how the access is held (directly, via a group or via a directory), the validity of a direct assignment and the latest certification outcome. Entries that deserve a look are flagged: no login for 90 days, an inactive or locked account that is still assigned, a direct assignment that expires within 30 days, access held through a group or directory that is not part of the workspace, and access the latest certification revoked but the person still holds. Direct assignments are marked as well. Search by application, user or access path and filter by a flag (both look through the whole list), revoke a direct assignment right there (subject to the workspace's access permissions), or download the list with Export attestation (CSV): one row per application and user, including the flags, as evidence for audits. The tab shows up to 500 matching entries; when the list is cut there, the counts next to the filter are marked with a + because they only cover the entries looked at so far. The export always carries the full list. Each export is recorded in the audit log.

The Actions menu at the top right holds:

  • Settings: name, description, an accent color for the workspace card and the Workspace members manage access switch.
  • Archive workspace / Unarchive workspace: an archived workspace is frozen. Its resources are kept, but application assignments, group memberships and role assignments of the workspace's resources can no longer be changed by anyone, full administrators included, until the workspace is unarchived. Directory synchronization and automated processes continue. An archived workspace accepts no new resources and is listed after the active workspaces. Its applications are no longer offered for access requests, and requests still open for them are rejected.
  • Sunset access (archived workspaces only): revokes every current assignment of the workspace's applications, for users, groups, organizations and directories, and triggers deprovisioning for connected applications. Group memberships themselves are kept, and API client grants and already issued tokens are not affected (tokens stay valid until they expire). The action requires confirmation and cannot be undone. It runs in the background: the page only confirms that the sunset started, and the result, with the number of removed and skipped assignments, is recorded in the workspace's audit log when the run finishes. Only one run per workspace happens at a time; a second attempt while one is running is rejected. Use it to wind a workspace down cleanly, for example at the end of a project.
  • Delete workspace (administrators only): deleting a workspace releases its resources. Alarms scoped to the workspace lose that scope; an alarm scoped to this workspace only then applies to its remaining conditions and no longer notifies workspace responsibles. If they were its only recipients, the administrator who deleted the workspace becomes a recipient. Each such change is recorded in the audit log.

License and downgrade

Workspaces require a license that includes them (Advanced, Pro, or the trial). If the license no longer includes Workspaces, for example after a downgrade, the Workspaces area is hidden and workspaces have no effect at all:

  • managed access and the archive freeze no longer apply,
  • members and responsibles lose the rights they held through a workspace, and
  • members fall back to what their access level allows instance-wide; Developer admins, for example, keep read access only and no longer manage applications, APIs, groups, authentication policies or roles (see Admin console users).

Workspaces, their people and their resource assignments are kept and take effect again as soon as the license includes Workspaces again.

Troubleshooting

  • "Access to this resource is managed by workspace members." The application or group belongs to a workspace with managed access turned on. Ask a workspace responsible to add you as a member with the right permission, or to make the assignment for you.
  • "This workspace is archived and its resources are frozen." The resource belongs to an archived workspace. Unarchive the workspace to make changes.
  • A resource can't be added to the workspace. It already belongs to another workspace. Remove it there first.
  • "An application with managed access can only be assigned to groups of its own workspace." The group belongs to another workspace or to none. Assign a group of this workspace, or ask an administrator to move the group into it.
  • "An application with managed access cannot be assigned to directories." A directory never belongs to a workspace, so its membership is not protected by it. Assign users, groups of the workspace or organizations instead, or turn off managed access.
  • "This authentication policy is used by an application outside this workspace." A policy can only be added to a workspace when no application outside it uses the policy. Bind that application to a different policy first.
  • "This group grants access to an application or role outside this workspace." Once a group is in a workspace, every member with Manage resources decides who joins it, so a group can only be added while all applications assigned to it and all its roles belong to the same workspace. Revoke the other assignments first, or add the application or role to the workspace as well.
  • "A role with managed access can only be assigned to groups of its own workspace." The role belongs to a workspace with managed access, and the group belongs to another workspace or to none. Attach the role to a group of the role's workspace.
  • "This application uses an authentication policy of this workspace." An application can only leave a workspace once it no longer uses one of the workspace's authentication policies, otherwise the workspace's members would keep control over its login requirements. Bind it to another policy first, or remove the policy from the workspace first.
  • "This group still grants access to an application of this workspace." A group can only be removed from a workspace with managed access (or an archived one) once none of the workspace's applications is assigned to it, otherwise its members would keep that access while the group's membership is no longer protected. Revoke the assignment, or remove the application from the workspace first.
  • A role is missing when attaching roles to a group. For admins below Operator the list only shows roles of workspaces in which they hold Manage resources.
  • A group's membership changed even though access is managed. Synced groups continue to receive membership from their directory; managed access governs manual changes made in the console or API.

See also

On this page