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

# Dashboard — Settings

> A tour of organization settings — members, integrations, agents, billing.

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:

<CardGroup cols={2}>
  <Card title="General" icon="circle-info">
    Org name, description, slug. Who can edit: **Owner / Admin**.
  </Card>

  <Card title="Members" icon="users">
    Add / remove / change roles. Who can edit: **Owner / Admin**.
    See [Invite the Team](/en/guides/invite-team).
  </Card>

  <Card title="Integrations" icon="plug">
    Connect Twilio, Composio, Tavily, Apify. Who can edit: **Owner /
    Admin**. Members can see the status (connected / not), but cannot
    change credentials.
  </Card>

  <Card title="Agents" icon="robot">
    Enable personas, configure per-agent spending caps, edit
    `voice_md`. Who can edit: **Owner / Admin**.
  </Card>

  <Card title="Billing" icon="credit-card">
    Balance, plans, packs, spending caps, Stripe portal. Who can view:
    **Owner / Admin**. Who can change plans / buy packs: **Owner** only.
  </Card>

  <Card title="Trust" icon="shield-check">
    Audit log, active sessions, personal data (LGPD). Owner +
    Admin can inspect; users see only their own personal audit
    entries.
  </Card>
</CardGroup>

## General — What You Can (and Cannot) Change

| Field                  | Changeable?                                                        |
| ---------------------- | ------------------------------------------------------------------ |
| **Display name**       | Yes. Shown in chat, email, and the portal.                         |
| **Description**        | Yes. Free text — included in the context agents read.              |
| **Logo** (upload)      | Yes. Shown in chat and email signatures.                           |
| **Slug**               | No. It's part of the URL — changing it would break external links. |
| **Country / timezone** | Yes. Affects outbound cadence defaults and WhatsApp number type.   |
| **Default language**   | Yes. Default voice for the org (pt-BR / es / en).                  |

<Warning>
  **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.
</Warning>

## Members — Quick Flow

<Steps>
  <Step title="Settings → Members → Invite">
    A dialog opens with 2 fields: email + initial role.
  </Step>

  <Step title="Set the initial role">
    Owner / Admin / Member / Viewer. See [Organizations](/en/concepts/organizations)
    for what each role can do.
  </Step>

  <Step title="Apollo Space sends the link">
    Single-use, expires in 7 days. The invitee clicks the link, creates
    an account, and lands inside your org.
  </Step>
</Steps>

Full details: [Invite the Team](/en/guides/invite-team).

## Integrations — What You Can Connect

| Integration         | Purpose                                   | Model                                          |
| ------------------- | ----------------------------------------- | ---------------------------------------------- |
| **Twilio WhatsApp** | Marcus sends WhatsApp messages            | BYO key                                        |
| **Resend / Gmail**  | Marcus sends email                        | BYO key (Resend) or OAuth (Gmail via Composio) |
| **Composio**        | 400+ SaaS apps (Notion, Slack, Linear...) | OAuth managed by Composio                      |
| **Tavily**          | Scout runs web searches                   | BYO key                                        |
| **Apify**           | Maps lead search + enrichment             | BYO key                                        |

<Info>
  **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).
</Info>

Detailed guides by integration:

<CardGroup cols={2}>
  <Card title="WhatsApp via Twilio" icon="comments" href="/en/guides/set-up-whatsapp">
    End-to-end setup (45 minutes to 7 days depending on Meta approval).
  </Card>

  <Card title="Composio" icon="puzzle-piece" href="/en/integrations/composio">
    OAuth + 400+ apps.
  </Card>

  <Card title="Tavily" icon="magnifying-glass" href="/en/integrations/tavily">
    Scout's public web search engine.
  </Card>

  <Card title="Apify" icon="map-pin" href="/en/integrations/apify">
    Maps + contact enrichment.
  </Card>
</CardGroup>

## Agents — Where to Configure Personas

For each agent (Scout / Marcus / Athena / Twin / custom), Settings
exposes:

<AccordionGroup>
  <Accordion title="Enable / Disable" icon="toggle-on">
    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.
  </Accordion>

  <Accordion title="Voice_md" icon="comment">
    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.
  </Accordion>

  <Accordion title="Per-agent spending caps" icon="gauge-high">
    Daily and monthly ceiling per agent. See [Caps](/en/billing/caps) for
    details on the 4 protection levels.
  </Accordion>

  <Accordion title="Enabled tools" icon="screwdriver-wrench">
    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).
  </Accordion>

  <Accordion title="Memory + Brain" icon="brain">
    Which Brain documents the agent can access. Default: all public org
    documents. Restriction: only documents with a specific tag.
  </Accordion>
</AccordionGroup>

## Billing — Common Shortcuts

<CardGroup cols={2}>
  <Card title="Change plan" icon="circle-arrow-up" href="/en/billing/plans-and-packs">
    Upgrade / downgrade via the Stripe portal.
  </Card>

  <Card title="Buy a standalone pack" icon="box" href="/en/billing/plans-and-packs">
    A Stars top-up that doesn't expire.
  </Card>

  <Card title="Configure caps" icon="gauge-high" href="/en/billing/caps">
    Ceilings by org / agent / user.
  </Card>

  <Card title="Wallet history" icon="receipt" href="/en/billing/stars">
    Append-only ledger — every transaction is auditable.
  </Card>
</CardGroup>

## 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](/en/trust/security) for the complete audit model.

## Next Steps

<CardGroup cols={2}>
  <Card title="Dashboard — Overview" icon="house" href="/en/dashboard/overview">
    What you see when you log in.
  </Card>

  <Card title="Trust — Multi-tenant" icon="shield-check" href="/en/trust/multi-tenant">
    How each org is isolated from others at the database level.
  </Card>
</CardGroup>