Skip to main content
On a new hire’s first day you’d hand over the org chart, the tone-of-voice guide, the list of tools they’re allowed to touch, and a spending limit. Settings is where you do exactly that — except the team you’re onboarding is Athena, your specialists, and your Digital Twin. Set the rules once here and every agent reads them before it acts, so you stop repeating the same instruction in every conversation.

​
What Lives in Settings

Settings is your organization’s configuration hub. Five main areas, each with appropriate role restrictions:

General

Org name, description, slug. Who can edit: Owner / Admin.

Members

Add / remove / change roles. Who can edit: Owner / Admin. See Invite the Team.

Integrations

Connect Twilio, Composio, Tavily, Apify. Who can edit: Owner / Admin. Members can see the status (connected / not), but cannot change credentials.

Agents

Enable personas, configure per-agent spending caps, edit voice_md. Who can edit: Owner / Admin.

Billing

Balance, plans, packs, spending caps, Stripe portal. Who can view: Owner / Admin. Who can change plans / buy packs: Owner only.

Trust

Audit log, active sessions, personal data (LGPD). Owner + Admin can inspect; users see only their own personal audit entries.

​
General — What You Can (and Cannot) Change

Changing the slug would require a URL migration — all external integrations (Twilio webhooks, Resend, proposal links generated by Marcus) point to URLs containing the current slug. This is not currently supported via the UI. If you need to do this, open a support ticket.

​
Members — Quick Flow

1

Settings → Members → Invite

A dialog opens with 2 fields: email + initial role.
2

Set the initial role

Owner / Admin / Member / Viewer. See Organizations for what each role can do.
3

Apollo Space sends the link

Single-use, expires in 7 days. The invitee clicks the link, creates an account, and lands inside your org.
Full details: Invite the Team.

​
Integrations — What You Can Connect

All integrations are opt-in. A new org starts with none connected. Connect only the ones you plan to use — unconfigured credentials mean the related feature simply won’t appear to agents (rather than showing a tool that errors out).
Detailed guides by integration:

WhatsApp via Twilio

End-to-end setup (45 minutes to 7 days depending on Meta approval).

Composio

OAuth + 400+ apps.

Tavily

Scout’s public web search engine.

Apify

Maps + contact enrichment.

​
Agents — Where to Configure Personas

For each agent (Scout / Marcus / Athena / Twin / custom), Settings exposes:
Turns the persona on or off for your org. Disabling does not delete history — it hides the persona from the interface and blocks new invocations.
Markdown describing the org or persona voice — tone, vocabulary, greeting, signature. Editable by the team, versioned, and audited. Agents re-read it on every conversation.
Daily and monthly ceiling per agent. See Caps for details on the 4 protection levels.
Which tools the agent can invoke. Each persona comes with sensible defaults — you can restrict them (e.g., remove web_search from Marcus if you want him to rely on Scout for research).
Which Brain documents the agent can access. Default: all public org documents. Restriction: only documents with a specific tag.

​
Billing — Common Shortcuts

Change plan

Upgrade / downgrade via the Stripe portal.

Buy a standalone pack

A Stars top-up that doesn’t expire.

Configure caps

Ceilings by org / agent / user.

Wallet history

Append-only ledger — every transaction is auditable.

​
Audit — What Gets Recorded

Every operation in Settings creates an entry in the org’s audit log — who, when, and what. Owner + Admin can inspect it; external auditors can be provisioned as Viewer with read access to the audit log. See Security for the complete audit model.

​
Next Steps

Dashboard — Overview

What you see when you log in.

Trust — Multi-tenant

How each org is isolated from others at the database level.