> For the complete documentation index, see [llms.txt](https://docs.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/aura-ai/aura-ai/aura-memory.md).

# Aura Memory

Aura Memory in **Rillet** retains your preferences across conversations, eliminating the need to repeat the same instructions in every session. Once a preference is saved, Aura applies it automatically in all future interactions.

### Save a Memory

Use either of these methods to save a memory in **Aura Assistant**.

#### **Option 1: Tell Aura to Remember a Preference**

Follow these steps to ask Aura to remember a preference:

{% stepper %}
{% step %}
Open **Aura** in the left navigation menu.
{% endstep %}

{% step %}
Select **Assistant** at the top of the Aura panel.

<figure><img src="https://612265232-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNpXFVFZpTQck3vIrjmHB%2Fuploads%2Fe0bles3PCJ3LNa4mVM7A%2Fimage.png?alt=media&#x26;token=544cb3ea-2795-435d-adae-329cc47ea819" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Type your preference into any message to Aura, using natural language, such as "Remember that I always want journal entries named as vendor, date, then a short description."

<figure><img src="https://612265232-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNpXFVFZpTQck3vIrjmHB%2Fuploads%2Fzg4ZJE5bXvweEd585e4e%2Fimage.png?alt=media&#x26;token=6796100f-6aff-42b9-a446-f70579855056" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

#### **Option 2: Save a Memory from a Message**

Take these steps to save a memory from a message you already sent:

{% stepper %}
{% step %}
Open **Aura** in the left navigation menu.
{% endstep %}

{% step %}
Select **Assistant** at the top of the Aura panel.

<figure><img src="https://612265232-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNpXFVFZpTQck3vIrjmHB%2Fuploads%2Fk5ykxXWi894FV9NXsA45%2Fimage.png?alt=media&#x26;token=6d5ee280-ec0e-4c18-bb22-19c02714e42f" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Hover over a message you sent and click the **Save to Aura Memory** icon.
{% endstep %}

{% step %}
Review the **Saved to memory** card, which summarizes what Aura saved.

<figure><img src="https://612265232-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNpXFVFZpTQck3vIrjmHB%2Fuploads%2FpycFtCwdMZ9O5vHuBUjK%2Fimage.png?alt=media&#x26;token=35ebce95-4f5a-4b46-bbfb-862d0da35e21" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

### View and Manage Saved Memories

Follow these steps to review or update what Aura remembers:

{% stepper %}
{% step %}
Click **Memory** in the Aura panel to open the **Memory** page.
{% endstep %}

{% step %}
Review the **Saved memories** list, which shows everything Aura has saved and the date each memory was saved.

<figure><img src="https://612265232-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNpXFVFZpTQck3vIrjmHB%2Fuploads%2FmuJifnD0NsCfdSswPzjL%2Fimage.png?alt=media&#x26;token=52d61def-d8c8-49bc-9647-2c0eb7d11279" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

From this page, you can edit or delete a saved memory with the icons beside it, or add a new one by typing it into the **Add memory** field and clicking **Save memory**.

### Explore Memory Examples by Category

Browse example memories grouped by preference type:

{% tabs %}
{% tab title="JE Naming" %}
Use these examples to set your preferred journal entry naming format:

* "Remember that I always want journal entries named as vendor, date, then a short description."
* "Remember to always list the entity name before the vendor name in journal entry titles."
* "Remember to keep journal entry descriptions short, no more than a few words."
  {% endtab %}

{% tab title="Terminology" %}
Use these examples to set your preferred terminology:

* "Remember to always use "deferred revenue" instead of "unearned revenue.""
* "Remember to always call it "MRR" instead of "monthly recurring revenue" in reports."
* "Remember to always refer to our fiscal year as starting in February."
  {% endtab %}

{% tab title="Report Formatting" %}
Use these examples to set your preferred report formatting:

* "Remember to always structure my board summaries the same way, with the same sections every time."
* "Remember to always start financial reports with a summary paragraph before the numbers."
* "Remember to always include a cash balance section in every report you generate for me."
  {% endtab %}

{% tab title="Flagging Thresholds" %}
Use these examples to set thresholds Aura should flag automatically:

* "Remember to flag any single transaction over $50K in a board summary."
* "Remember to flag any vendor bill over $10K for review."
* "Remember to flag any journal entry posted outside of business hours."
  {% endtab %}

{% tab title="Default Fields" %}
Use these examples to set default fields for recurring actions:

* "Remember to always use Mercury Checking as the cash account when creating invoices."
* "Remember to always assign new SaaS revenue to the Enterprise customer segment."
* "Remember to always use the same revenue account for recurring subscription invoices."
  {% endtab %}

{% tab title="File Analysis" %}
Use these examples to set how Aura should analyze files you upload:

* "Remember to always summarize the top vendors by spend when I upload a spend file."
* "Remember to always highlight the termination clause when I upload a contract."
* "Remember to always flag renewal dates when analyzing uploaded contracts."
  {% endtab %}
  {% endtabs %}

### Frequently Asked Questions (FAQs)

<details>

<summary>What kinds of preferences should I save?</summary>

These work well for recurring, implicit preferences that finance teams tend to carry around but rarely write down. Once a preference is saved, you do not need to restate it at the start of every session, or correct Aura's output and hope it sticks next time.

</details>

<details>

<summary>Where do saved memories apply?</summary>

Saved memories are picked up automatically in both **Aura Assistant** and **Aura Agents**, so a preference you save once carries through everywhere you use Aura, without needing to set it up separately in each surface.

</details>

### See Also

To learn more about Aura in **Rillet**, review these articles:

* [**Getting Started with Aura Assistant**](/EjmEP4KZ9BVp9j2ho4Mh/aura-ai/aura-ai/getting-started-with-aura-assistant.md)
* [**Aura Activity**](/EjmEP4KZ9BVp9j2ho4Mh/aura-ai/aura-ai/aura-activity.md)
* [**Aura Agents**](/EjmEP4KZ9BVp9j2ho4Mh/aura-ai/aura-ai/aura-agents.md)
* [**Assistant vs Agent**](/EjmEP4KZ9BVp9j2ho4Mh/aura-ai/aura-ai/assistant-vs-agent.md)
* [**Aura AI Prompt Examples**](/EjmEP4KZ9BVp9j2ho4Mh/aura-ai/aura-ai/aura-ai-prompt-examples.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/aura-ai/aura-ai/aura-memory.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.