Skip to content

Teams, Workspaces, and Business Scopes

Overview

Use Organization > Overview to group users into Teams, organize access through Workspaces, and define reusable Business Scopes.

Availability and write actions can vary by tenant rollout and assigned permissions.

Teams

  1. Open Organization > Overview > Teams.
  2. Select Create team.
  3. Enter Team name, Slug, and optional Description.
  4. Select a Team persona and Owner.
  5. Optionally choose a Primary workspace.
  6. Add Users and select a Membership role.
  7. Link supported Business Scopes.
  8. Review the summary and save.

The team detail view can show Members, Business Scopes, and Entitlements.

Workspaces

  1. Open Organization > Overview > Workspaces.
  2. Select Create workspace.
  3. Enter Workspace name, Slug, and optional Description.
  4. Choose the Workspace type and owner.
  5. Link Business Scopes or saved mappings.
  6. Add existing teams and candidate resource categories when available.
  7. Review the summary and save.

The form explicitly distinguishes workspace setup context from access enforcement. A workspace does not automatically create broad grants.

Business Scopes

  1. Open Organization > Overview > Business Scopes.
  2. Search saved Virtual Tags or select Create Business Scope.
  3. Enter Business Scope name and select the scope type.
  4. Configure the supported mapping or definition.
  5. Save the Business Scope.
  6. Use Attach to connect it to a team, workspace, or resource.

Attaching a Business Scope does not itself grant access. Entitlements still control access.

Best practices

  • Use stable, business-owned names and slugs.
  • Assign an accountable owner to every team and workspace.
  • Keep Business Scopes aligned with Perspectives and Virtual Tags.
  • Review inherited entitlements before adding direct access.
  • Treat setup-context warnings literally; confirm enforcement before relying on a new relationship.

Troubleshooting

If create or edit controls are disabled, the write endpoint may not be enabled or your user may lack permission. Refresh before retrying; the UI states that failed verification does not change existing access settings.