Keep control

Changes and approvals

People and their agents can suggest changes to your Mind. You see what would change, and the rules you set decide whether it is saved straight away or waits for someone to approve it.

Contents
System mapHow a suggestion becomes a change

An agent prepares the edit. Your rules decide whether it waits for a person, and every step is recorded.

  1. Agent suggests an edit

    new wording and the reason

  2. Held for review

    approve or reject

  3. Save the file

    only when approved or allowed

  4. Keep earlier versions

    see what changed

  5. Record it

    who did what and when

Who can change a file

Someone may be able to read a zone without being able to change it. The owner chooses who may suggest changes, who may approve them, and which changes need approval at all.

Agents usually suggest a change for a person to review.

How a change is suggested

A suggestion shows the new wording against the current file, with the reason for the change and who prepared it.

If the rules say it must wait, it is held: nothing in your Mind has changed yet. If the rules allow it, it is applied and saved straight away.

Review before saving

A person allowed to approve can approve a held change or reject it. A check before submission can catch a suggestion written against an older version of the file. If the file has changed since, review the current version; a change that clashes with newer edits isn't saved.

Approved changes are saved with the earlier versions still in the history.

See who did what

Reads, refusals, suggestions and approvals each leave a short activity record.

Activity records are signed and chained together. They show who acted, what kind of action it was, the area, when, and the outcome, without storing the request text or the protected information.

Related

Suggest a correction and check its result · Know what an agent may read or change

Practical guides for people and agents

Start with one useful job

Join the waitlist

Plain text for AI agents. Same content as the human page.

## For agents

- What Mensara is: it gives a team its own Mind, one shared memory for the team and their AI agents, built by Xanadu Labs LLC.
- Status: signup is not open. A person joins the waitlist at https://app.mensara.ai/#waitlist. Agents cannot create an account or sign up.
- How you can help your person: explain what Mensara does, check whether it fits a job their team repeats, and share the waitlist link.
- Agent references: https://app.mensara.ai/llms.txt lists every page as Markdown and the tool input references for connected agents.

---

# Changes and approvals

How Mensara works · Keep control · [How it works](https://app.mensara.ai/how-it-works)

People and their agents can suggest changes to your Mind. You see what would change, and the rules you set decide whether it is saved straight away or waits for someone to approve it.

### How a suggestion becomes a change

An agent prepares the edit. Your rules decide whether it waits for a person, and every step is recorded.

1. Agent suggests an edit: new wording and the reason
2. Held for review: approve or reject
3. Save the file: only when approved or allowed
4. Keep earlier versions: see what changed
5. Record it: who did what and when

## Who can change a file

Someone may be able to read a zone without being able to change it. The owner chooses who may suggest changes, who may approve them, and which changes need approval at all.

Agents usually suggest a change for a person to review.

## How a change is suggested

A suggestion shows the new wording against the current file, with the reason for the change and who prepared it.

If the rules say it must wait, it is **held**: nothing in your Mind has changed yet. If the rules allow it, it is **applied** and saved straight away.

## Review before saving

A person allowed to approve can approve a held change or reject it. A check before submission can catch a suggestion written against an older version of the file. If the file has changed since, review the current version; a change that clashes with newer edits isn't saved.

Approved changes are saved with the earlier versions still in the history.

## See who did what

Reads, refusals, suggestions and approvals each leave a short activity record.

Activity records are signed and chained together. They show who acted, what kind of action it was, the area, when, and the outcome, without storing the request text or the protected information.

## Example: An agent suggests a policy change

An agent finds a leadership decision that changes the refund period from 14 to 30 days. It prepares an edit to the refund policy that links to the decision. The owner sees the current wording and the proposed wording, and the file changes only after they approve it.

## Status: Available now

STATUS · CHECKED 3 OCTOBER 2026

Suggested changes, held and applied outcomes, approval, file history and signed activity records are available on configured Minds. An activity record shows what your Mind did; it can't prove that an outside email or document was true.

## Related

- [Suggest a correction and check its result](https://app.mensara.ai/how-it-works/suggest-a-correction)
- [Know what an agent may read or change](https://app.mensara.ai/how-it-works/read-and-propose)

Previous page: [Skills, apps and automations](https://app.mensara.ai/how-it-works/skills-apps-automations)

Next page: [Backup, restore and ownership](https://app.mensara.ai/how-it-works/backup-restore-ownership)

Keep a second copy and recover your Mind if something fails.

[Join the waitlist](https://app.mensara.ai/#waitlist)