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

# History coverage

> Recorded actions, attribution, and the limits of per-object History for supervision.

History is a per-object view of the firm's audit log. Entries record an action, when it happened, who acted, the objects concerned, and a reference to what caused it. Settings entries include changed fields with before and after values.

Entries cannot be edited or deleted. A later change creates a new entry; it does not rewrite the earlier record.

For instructions on finding and reading entries, see [See who changed an account and why](/advisor/see-who-changed-an-account).

## Recorded actions

Each page shows entries for that object. To review a model change, for example, open the model's History rather than a client's History.

| Area | Recorded outcomes |
| - | - |
| Firm settings | Changes to order policy, factor values, and default customization settings. |
| Account settings | Changes to tax account type, external ID, metadata, reporting benchmark, assigned model, account customization, and sleeve settings. |
| Model settings | Changes to model settings and sleeve allocations, including draft and deployed status. |
| Sleeve settings | Changes to sleeve settings, including archiving and restoring a sleeve. |
| Trade proposals | A proposal becoming ready for review, failure to produce a proposal, approval, and marking a proposal executed. |
| Custodian trade instructions | Approval of trades for the custodian and subsequent instruction status changes, including sending, completion, partial sending, refusal, and cancellation. |
| Changes drafted by Tilt Agent | A saved change proposal being created, applied, discarded, or not applied because the saved value changed first. Applying a settings change also records the settings change itself. |
| Tilt actions | Creation, constituent and score analysis, edits, re-analysis, publication, deletion of an unpublished draft, archiving, restoration, rationale changes, and scheduled rebalances. |
| Automation runs | Finished firm automation runs, including successful runs, failed runs, and runs that changed nothing. Entries reach subscribed objects and their containing client or household where applicable. |

Approval and execution are separate outcomes. An approval entry alone does not establish that orders were sent or filled. Check the instruction and order statuses when reviewing trading activity.

## Who acted and why

| Actor | What History shows |
| - | - |
| A person | The person's recorded email address. |
| A Tilt Agent run | **Tilt Agent**, with the person it acted for. |
| The system | **Tilt**. |

Each entry references the request, conversation message, reviewed change proposal, automation run, or scheduled job that caused it. This reference may not include a written investment rationale. You can open a linked conversation if you have access; the audit entry itself does not contain the transcript.

Entries keep object names as recorded at the time of the event, after the change. A rename therefore uses the new name, with old and new values in its change details when recorded. Later renames, deletions, and household moves do not rewrite these saved names. Older entries without saved names can use current names or a generic label such as **An account**.

## Activity outside History

Tilt's recording rule covers saved changes, decisions, and connected-system actions that affect clients, accounts, households, or the firm's rules, whether a person, Tilt Agent, or the system acts. The coverage gaps below apply to that rule.

Opening pages, reading data, previewing changes, and editing unsaved drafts do not create entries. Neither do retries without a new outcome, personal layout changes, or thumbs-up and thumbs-down chat feedback. A clarification in chat can lead to a saved change without becoming a separate History entry. Tilt records saved change proposals and finished automation runs, including runs with no changes.

Current coverage has these limits:

* Household membership changes are not recorded as their own actions.
* Connected-app tool approvals, permission changes, and writes are not currently included in this History coverage, even though committed outcomes and permission changes fall within the recording rule.
* Account settings entries do not provide a history of every holdings or market-value update.

## Using History for supervision

Tilt delivers some entries, such as change-proposal reviews and automation outcomes, separately from the original save. History therefore cannot guarantee an entry for every completed action.

An empty History or a missing row does not establish that no action occurred. Compare the object's saved state, the source conversation when available, and proposal or custodian order records as appropriate. History's append-only entries do not by themselves establish a regulatory retention period or that your firm's recordkeeping obligations are met.


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