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

# Settings and administration

> Manage personal mail preferences, workspace identity, members, Aurora, and desk memory.

Open Settings from the header on desktop or the user menu on a phone.

| Tab | Who can view it | Who can change it |
| - | - | - |
| Profile | Every member | Read-only |
| Mail | Every member | The current member |
| Workspace | Every member | Admin and Owner |
| Members | Admin and Owner | Admin and Owner, with Owner-only ownership transfer |
| Invitations | Admin and Owner | Admin and Owner |
| Aurora | Every member | Admin and Owner |
| Notebook | Every member | Every member, with limits on autonomy proposals |

## Profile

Profile shows your name, email, avatar or initials, and current role. It has no controls for changing those values.

## Mail

Each member manages two personal preferences:

* **Signature**: add, edit, or delete one rich-text signature. It is inserted into new messages, replies, and Reply all drafts written by that member.
* **Reading pane**: choose No split, Right, or Bottom. Phones always use the single-view mail flow.

The personal signature is not Aurora's signature. Aurora uses the desk name and contact details from Workspace.

## Workspace

Every member can read the workspace record. Admins and owners can edit:

* The IANA time zone.
* Agency name, phone, email, and mailing address.
* Surplus-lines licence type, number, holder, broker, and optional broker NPN.

The customer and workspace name shown at the top is read-only.

The workspace time zone controls Aurora's desk clock and the nominal local time for:

* Renewal initiation at 6:00 AM.
* Morning briefing at 7:00 AM.
* Invoice dunning at 8:00 AM.

The scheduler checks once per UTC hour. In a half-hour or quarter-hour time zone, a local-time job can run at `:30` or `:45` rather than exactly on the hour. Some policy and accounting dates still use UTC dates.

## Members

Members lists active users. An admin or owner can change another non-owner member between Contributor and Admin, or deactivate them. There is no restore control after deactivation.

Only the current owner can transfer ownership. The selected member becomes Owner and the former owner becomes Admin. A member cannot change their own role from this table.

## Invitations

Create an invitation with the person's name, email, and Contributor or Admin role. Owner cannot be assigned at invitation time.

An invitation link is valid for 24 hours. **Resend** invalidates the earlier token and starts a new 24-hour window. **Cancel** invalidates the link and removes it from the pending table. Accepted, cancelled, and expired invitations are not retained in a visible history.

Invitation acceptance creates a new user and starts their session. It cannot attach an invitation to an existing user with the same email address.

## Aurora

Every member can read the charter. Admins and owners can move its seven configurable actions between Approval required and Automatic:

* Outbound email.
* Quote letters.
* Quote withdrawals.
* Billing notices.
* Declinations.
* Binding.
* Endorsements.

Billing notices default to Automatic; the others default to Approval required. Collection-link creation is not a separate charter row. It is a direct record action, while the email carrying the link follows Outbound email.

**Pause Aurora** stops background file turns across the workspace. New requested turns wait, but interactive rail chat still answers. Resume queues immediate and overdue turns.

> [!WARNING]
>
> Pause does not stop renewal creation, morning briefing, dunning, invoice notices, scheduled cancellation execution, or
> other system jobs.

See [Aurora and approvals](https://docs.useunderflow.com/platform/aurora.md) for the action boundary.

## Notebook

The desk notebook has two fixed pages: Style guide and Working preferences. Any member can replace a page's Markdown; the history records the editor and reason, but there is no one-click restore.

Aurora can propose a memory addition, autonomy change, or program-guideline addition from the desk's corrections. Any member can adopt memory or guideline additions and dismiss a proposal. Only an admin or owner can adopt an autonomy change.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.