Documentation

Settings overview

A map of every organization settings screen, grouped as the interface groups them.

Organization settings are grouped into six areas. This page maps them; each linked article covers one in detail.

Most settings have workable defaults. The ones worth attention on day one are members, source control, and — if you have your own model contracts — provider keys.

Workspace

SettingWhat it controls
GeneralOrganization name and identity
MembersWho has access, and their role
AI profileWhich models back which agents — see AI profiles
Provider keysYour own model provider credentials
Service accountsNon-human identities for programmatic access

Connections

Source control connections, chat platform bots and bridges, and external MCP servers with their templates and analytics.

See the Integrations overview.

Automation

Event automations and webhooks with their templates, delivery log and analytics; and Coroid's own MCP server — client setup, access tokens, approvals and automation policies.

See Hooks.

Security and access

SettingWhat it controls
Enterprise identitySSO/SAML and SCIM provisioning
Org policyOrganization-wide constraints on what work may do
Active sessionsWho is signed in, and revoking access
Security activityThe security event feed
Audit logEvent history and SIEM export

Billing and usage

Usage, capacity and credits, detailed reports, plan and subscription management, and billing history. See Plans and pricing.

SettingWhat it controls
StorageProviders, regions and capacity
Data retentionHow long things are kept, and purging
Export settingsPortable configuration bundles
Terms and privacyWhich terms you have accepted

Who can change what

Roles are OWNER, ADMIN, MEMBER and REVIEWER. Owners hold full control including billing and deletion; admins hold everything short of the owner-only destructive actions.

Resist making everyone an admin. Provider keys, policies and retention are organization-wide, and the blast radius of a mistake in them is every project at once.