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

EmailOS can use approved context to make prepared work fit your team, while access stays tied to a clear purpose and visible review.

## What learning means

Learning means EmailOS uses permitted examples and context to improve prepared work, such as matching a team’s writing style. Your team chooses the source and purpose.

Learning works best when a person can inspect the result. If a draft feels wrong, check the chosen source before adding more context.

## Choose a source

Start with the smallest source that answers the task. Approval should name the purpose, included items, and people who may review the result.

Keep private knowledge separate from shared team context. If the scope is unclear, leave the source off and ask the responsible owner to clarify it.

## Review access changes

Review access whenever the source, purpose, audience, or device changes. Earlier approval does not make a new use appropriate.

Narrow the source or purpose through your team’s normal settings process. To remove access, revoke the source and review the next prepared result.

If EmailOS declines a request, read the explanation. Correct the relevant scope or choose another allowed source.

## Read a receipt

A Lithi Receipt is a visible record that a governed action was recorded. It helps you match an action to its time, outcome, approved scope, and next step.

Receipts contain metadata, not the work itself. They do not include inbox messages, drafts, prompts, retrieved passages, secrets, or unredacted customer content.

A receipt supports review. It does not grant access, prove a source is complete, or make a result suitable without your check.

Use a receipt to answer a narrow question about a recorded action. Check its time, outcome, scope, and visible next step. Then return to the underlying work and review the source that informed it.

If the receipt does not match the action you expected, stop and check the account, source, and current access. Do not use a familiar label as a reason to skip the review. Ask the responsible owner when the record and the work do not line up.

## Keep privacy boundaries

Access follows the scope your team chose. Removing access means future work must be checked against the new boundary.

Keep private messages and draft bodies with the product that owns them. Share the smallest cited fact or rule needed for a task.

When a source changes, check the next result again. Do not treat an earlier answer as newly authorised context.

## Choose the next check

Start with one allowed source and one clear task. For the setup path, read [Get started](/docs/get-started). For the broader concept, return to [How EmailOS works](/docs/emailos/how-it-works).

If you need immediate troubleshooting, return to [the current setup guide](/docs/get-started).