Settings

Settings are workspace defaults for audit retention, policy refresh, and rule-bundle history inside an existing workspace.

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.update 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. Review changes in audit before and after a rollout.

Workspace configuration keys

These keys control retention, policy sync, and bundle history.

You list and set these keys when you configure workspace defaults.

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.

dome workspaces config list
dome workspaces config set --key audit.retention_days --value 90
dome workspaces config set --key authorization.rule_sync_interval --value 15s

GET /v1/config/{key}?workspace_id={{WORKSPACE_ID}}
PUT /v1/config/{key}

List the workspace configuration. Set workspace config key "audit.retention_days" to "90".

Every write emits a workspace.config.update event with previous and new values. Sensitive values use <redacted> in the audit payload.

Review changes

Query configuration changes before and after a rollout.

dome audit query \
  --types workspace.config.update \
  --primary-resource-kind workspace

Use Audit events to filter the full configuration history.

Next steps

• Manage Access
• Prepare Environments
• Audit events — filter on workspace.config.update