Skip to main content

Overview

Each workspace carries its own configuration. Unset keys resolve to their defaults. Set only values that differ from the platform baseline, and validate each change against the supported range before rollout. Configuration writes are audited. Every write emits a workspace.config.changed event with previous and new values. Sensitive values use <redacted> in the audit payload. The typical workflow is:
  1. List or set workspace defaults for the keys you need to change.
  2. Optionally tune token lifetime via identity.token_ttl for agent access tokens.
  3. Review changes in audit before and after a rollout.
The sections below explain the keys you can set and how token lifetime relates to other sessions.

Workspace configuration keys

These keys control retention, policy sync, bundle history, and agent token lifetime. You list and set these keys when you configure workspace defaults.

Token lifetime

identity.token_ttl controls tokens returned by Identity.ExchangeToken. New exchanges read the current value without restarting services. Use shorter lifetimes for ephemeral jobs. Increase the value only when refresh overhead justifies the larger exposure window. Dashboard sessions, credential links, and upstream OAuth tokens use separate lifetimes. Set the value with the same configure workspace defaults operation used for other keys.

Requirements

Before you begin, authenticate the Dome CLI and select a workspace context.

Permissions

Workspace settings writes require an admin role (or equivalent cascade) with config.manage. Each operation states the permission it requires. For exhaustive flags, tool parameters, and endpoint contracts, refer to the CLI, MCP, and API references.

Configure workspace defaults

List or set workspace configuration keys. Unset keys resolve to their defaults. Set only values that differ from the platform baseline.
Requires workspace admin (or an equivalent cascaded role) with config.manage.
Reference: dome workspace
Every write emits a workspace.config.changed event with previous and new values. Sensitive values use <redacted> in the audit payload.

Review changes

Query configuration changes before and after a rollout.
Use Audit events to filter the full configuration history.

Next steps