> ## Documentation Index
> Fetch the complete documentation index at: https://docs.domesystems.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage

> Configure platform defaults, access, environments, integrations, and data exports

**Manage** administers the Dome platform. You configure workspace defaults, who can administer Dome, tenants and workspaces, enterprise identity and secrets, and audit export.

Refer to [Scopes](/concepts/platform/scopes) concept for tenancy boundaries and [Permissions](/concepts/platform/permissions) concept for platform RBAC versus runtime agent authorization.

## How Manage administers the platform

The following capabilities are what you configure for platform administration:

* **Settings** set workspace defaults such as audit retention, policy refresh, and agent token lifetime. They apply inside an existing workspace. They do not create tenants or memberships.
* **Access** assigns workspace roles and scoped platform API keys for people and automation. These grants do not authorize agent tool or model calls.
* **Environments** create tenants and workspaces, select a CLI context, or provision a disposable sandbox. Organization provisioning stays outside this surface.
* **Integrations** connect SSO for platform users and store secrets Dome injects at egress. They do not attach agent-facing tools or models, and they do not configure export destinations.
* **Export** configures destinations, formats, schedules, and forwarder health so retained audit records reach your SIEM or object store. Investigation still happens under [Operate](/operate).

Manage is supporting administration. Connect and Govern decide what agents can reach and do. Operate makes that activity visible.

The typical workflow is:

1. [Configure platform](/manage/settings) to list or set workspace defaults, optionally tune token lifetime, and review configuration changes in audit.
2. [Manage access](/manage/access) to assign workspace members and create or revoke scoped platform API keys.
3. [Prepare environments](/manage/environments) to create tenants and workspaces, select a CLI context, or provision a sandbox when you need a throwaway try-out.
4. [Integrate systems](/manage/integrations) to configure single sign-on and store integration secrets.
5. [Export data](/manage/export) to choose a format, configure a destination, schedule runs, and monitor forwarder health.

If you are standing up a new boundary, start with [Prepare Environments](/manage/environments) before Settings and Access. Those pages assume a workspace already exists.

## Next steps

* [Connect](/connect) to register agents, attach resources, and route requests through Gateways
* [Govern](/govern) to authorize actions, set usage limits, and inspect content
* [Operate](/operate) to investigate audit events, stream live events, and subscribe to events
* [Develop](/develop) to send runtime credentials, Gateway endpoints, and Act-As envelopes from the application