Settings guide

Settings is the company control plane. Use it to manage members, invites, providers, channels, local-agent access, and operating defaults.

Setup order

Start with members and invites, then provider and channel connections, then MCP or CLI access. Do not connect tools for an agent seat until the Charter and Steward are clear.

What belongs in Settings

• Company profile and workspace defaults.
• Members, invites, and tenant roles.
• Agent access tokens for local agents.
• Provider and integration configuration.
• Slack channels (the channel bindings that route escalations, Sync Briefs, and reports to a seat or cluster).
• Connected machines (the paired Runners that run scheduled local work orders).
• Stored credentials (vault references only) and tool access approvals.
• Operating defaults, including Sync Brief scope.

Sync Brief scope

The weekly Sync Brief compiles either company-wide or per cluster. Company-wide is one brief covering the whole company and is the default for a new company. Per cluster compiles one brief per cluster, scoped to each cluster's seats; pick it when clusters run their own weekly sync. Per cluster falls back to a single company-wide brief when the company has no clusters, so the rhythm never produces zero briefs. The owner sets this at onboarding and can change it later in Settings.

Inference budget

Agents that run on ROST-managed inference draw against a tenant inference budget with a hard cap. A new company starts with a hard cap of $0, so a managed-inference run is blocked until the cap is raised. When a run hits the cap it stops with a typed budget error that names the fix; raise the cap before agents can run again.

• Set the hard cap with settings.update (CLI: rost settings update --hard-cap-usd <amount>). The optional soft cap warns before the hard cap and must be less than or equal to it.
• The sandbox dry run is free and is never blocked by the cap, so a fresh company can charter, dry-run, and take an agent live before setting a budget. The cap applies only to real managed-inference runs.
• A company that brings its own provider key (BYOK) is metered on that key and is not subject to the ROST-managed hard cap.

Agent guidance

Agents may explain which setting is needed and why. They should not ask users to paste secrets into chat or tool arguments. When credentials are required, route the user to the vault-backed setup flow.