See the complete route index at https://crusible.dev/llms.txt before following links.

# Settings

The two Settings scopes — what is yours alone, and what belongs to the workspace — and what each pane in them is for.

<!-- https://crusible.dev/docs/admin/settings/ · doctype: reference · role: admin · reviewed: 2026-09-05 -->


Settings opens from the bottom of the channel list, below the channels
themselves, and it opens on your profile. Its left column carries two groups,
and the split between them is the whole model:
**My settings** is personal to whoever is signed in, and
**Account**, below it, is the workspace.

Each **Account** pane is opened by its own permission rather than by one role,
and a pane you may not open is absent from the column rather than shown and
disabled. The panes you see are the ones you hold, so a colleague seeing fewer
than you holds fewer — the column does not say which are missing. See
[Roles and permissions](/docs/admin/roles-and-permissions/).

## The panes

| Pane                                   | Group       | What it holds                                                                       |
| -------------------------------------- | ----------- | ----------------------------------------------------------------------------------- |
| **My profile**          | My settings | Your profile, availability, status and the sign-in methods the account is linked to |
| **Notifications**       | My settings | Channels and alert preferences                                                      |
| **My history**          | My settings | Your own past sessions, ready to replay                                             |
| **Appearance**          | My settings | Themes, density and interface preferences                                           |
| **Directory**           | Account     | Everyone in the workspace, the access they hold, and the invitations still open     |
| **Providers**           | Account     | The compute providers this workspace can reach                                      |
| **SSO**                 | Account     | Enterprise single sign-on, and the workspace owner alone opens it                   |
| **Connections**         | Account     | SSH hosts, dev containers and databases                                             |
| **Credits and billing** | Account     | Usage, plans and invoices                                                           |
| **Integrations**        | Account     | The outside tools that back surfaces, grouped by what they are for                  |

**Planned.** Five of the ten panes hold nothing yet.

**My history**, **Providers**,
**Connections**, **Credits and billing** and
**Integrations** each open on a blurred picture of the pane, one
sentence, and a disabled **Coming soon** control. What the table
records against those five is what the pane is designed to hold, not what it
shows today.

Roles and invitations are not a pane of their own:
**Directory** carries the roster, the seats it consumes and the
invitations that have been sent and not accepted, in one place.

## What sits behind four of them

**My profile** carries the display name, the bio and the avatar,
and under them the sign-in methods: GitHub, Google and Microsoft each show
either the account they are connected as or an invitation to connect one.

**Planned.** **My history** holds no sessions yet: the pane
reads
“Every session you run will land here, ready to replay.”
above a disabled **Coming soon** control.
 What it
is designed to hold is a member's own record and nobody else's: a
**Session history** list —
“Rewind any terminal session and watch it pour again”
— grouped by when each session ran, with an **Export all** control above it.
Each session carries its start time, a status of **Completed** or **Error**, a
duration, a count of the commands it ran, and the first of those commands.
Opening one plays it back: an action log of every command, searchable and
filterable by the kind of command, against a scrubber with a speed control.

**Appearance** carries five theme modes — **System**, **Warm paper**,
**Ember**, **Aurora** and **Matrix** — each previewed as a miniature terminal
rather than a colour swatch, and below them density and the agent avatar set.
Density is
“How tight the workspace packs — type, rows, and spacing scale together.”
across three steps: **Compact**, **Default** and
**Comfortable**. The four
avatar sets keep one colour per
<a class="docs-term" href="/docs/reference/glossary/#discipline">discipline</a>, so changing set never
changes which colour means which kind of work.

**Providers** and **Integrations** are two different things with similar names.
**Planned.** Neither pane holds a row yet: **Providers** reads
“Connect a compute provider, then choose where each run lands.”
and **Integrations** reads
“Connect GitHub, Linear, Slack and the rest, and keep their keys in one place.”
above a disabled **Coming soon** control.
 What
they are designed to hold differs. **Providers** holds the machines the
workspace runs on: Cloud, Docker, Kubernetes and SSH, each reading
**Connected** or **Not connected**. **Integrations** holds the outside tools
that back a <a class="docs-term" href="/docs/reference/glossary/#surface">surface</a>, grouped by what
they are for — source control, project management, communication, monitoring,
and the model provider behind the agents.

## What Settings does not carry

Settings is workspace chrome. A channel's own configuration — its members, its
**Access** policy, its <a class="docs-term" href="/docs/reference/glossary/#signal-dial">signal dial</a>,
its enabled surfaces and its archive control — is in that channel's settings
pane, not here, and is set per channel.