Set safe boundaries

Know what an agent may read or change

Reading information, suggesting a change and deciding a request are different actions in Mensara. Your connected agent uses your account’s permissions; a proposal is an edit suggested for the Mind to check. This guide helps you recognise what an agent may do and choose the right response to a request in your Inbox.

Content updated .

Contents

Separate the permissions

An agent helping with a meeting may be allowed to read the relevant account records without being allowed to read payroll, alter every source or approve its own edits. Zones and permissions explains the information boundary.

A permitted edit can save immediately or wait for review according to the Mind’s settings. By default it saves without a person only when an automatic check passes and the proposer’s trust level and the area’s own limit allow it; deleting or renaming a file always waits for an approver (the owner, or an admin where approvals are delegated). Submitting it does not establish which result occurred.

Read the type of request

The Portal is the Mind’s web interface. Open Inbox for work needing a human. It combines held changes with other work, including questions, loop waits and records needing review. Feed also shows work needing your attention.

A question asks for information or a choice. A proposal asks to change something. A loop wait concerns a particular running case. Read the request and its evidence before choosing a response; one kind of answer does not automatically decide every related item.

Decide a proposal

Open the intended request, compare the proposed difference with the current record, and read the supporting evidence. If you have authority, use that request’s approve or reject controls. If it asks for exact human confirmation, answer the specific request you have just read.

After approval, inspect the actual result and read the saved record. Review changes and check what was saved gives the complete review sequence.

Answer a question or wait

Read what is being asked, the available options and the work it will resume. Supply the missing fact or choose the intended option through the request’s supported controls. An answer may allow work to continue, so check what the request says will happen next.

If you lack the authority or evidence, ask the named owner to decide. Do not turn an uncertain answer into a confident instruction merely to clear the Inbox.

Recheck after an interruption

A failed or incomplete Inbox read does not prove that nothing is waiting. A lost response after a decision does not prove that the decision failed. Reopen the original request and check its state before answering it again. Keep its reference with the handoff.

Related

Review changes and check what was saved · Understand your Mind’s settings · Understand activity and the history of a 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://www.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://www.mensara.ai/llms.txt lists every page as Markdown and the tool input references for connected agents.

---

# Know what an agent may read or change

Content updated 29 October 2026.

Guides · Set safe boundaries · [How it works](https://www.mensara.ai/how-it-works)

Reading information, suggesting a change and deciding a request are different actions in Mensara. Your connected agent uses your account’s permissions; a proposal is an edit suggested for the Mind to check. This guide helps you recognise what an agent may do and choose the right response to a request in your Inbox.

[Page as Markdown](https://www.mensara.ai/how-it-works/read-and-propose.md)

[Operating procedure](https://www.mensara.ai/how-it-works/review-requests-procedure)

## Separate the permissions

An agent helping with a meeting may be allowed to read the relevant account records without being allowed to read payroll, alter every source or approve its own edits. [Zones and permissions](https://www.mensara.ai/how-it-works/zones-and-permissions) explains the information boundary.

A permitted edit can save immediately or wait for review according to [the Mind’s settings](https://www.mensara.ai/how-it-works/mind-settings#why-changes-wait-for-review). By default it saves without a person only when an automatic check passes and the proposer’s trust level and the area’s own limit allow it; deleting or renaming a file always waits for an approver (the owner, or an admin where approvals are delegated). Submitting it does not establish which result occurred.

## Read the type of request

The Portal is the Mind’s web interface. Open **Inbox** for work needing a human. It combines held changes with other work, including questions, loop waits and records needing review. **Feed** also shows work needing your attention.

A question asks for information or a choice. A proposal asks to change something. A loop wait concerns a particular running case. Read the request and its evidence before choosing a response; one kind of answer does not automatically decide every related item.

## Decide a proposal

Open the intended request, compare the proposed difference with the current record, and read the supporting evidence. If you have authority, use that request’s approve or reject controls. If it asks for exact human confirmation, answer the specific request you have just read.

After approval, inspect the actual result and read the saved record. [Review changes and check what was saved](https://www.mensara.ai/how-it-works/changes-approvals-receipts#review-one-proposal) gives the complete review sequence.

## Answer a question or wait

Read what is being asked, the available options and the work it will resume. Supply the missing fact or choose the intended option through the request’s supported controls. An answer may allow work to continue, so check what the request says will happen next.

If you lack the authority or evidence, ask the named owner to decide. Do not turn an uncertain answer into a confident instruction merely to clear the Inbox.

## Recheck after an interruption

A failed or incomplete Inbox read does not prove that nothing is waiting. A lost response after a decision does not prove that the decision failed. Reopen the original request and check its state before answering it again. Keep its reference with the handoff.

## Related

- [Review changes and check what was saved](https://www.mensara.ai/how-it-works/changes-approvals-receipts)
- [Understand your Mind’s settings](https://www.mensara.ai/how-it-works/mind-settings)
- [Understand activity and the history of a change](https://www.mensara.ai/how-it-works/activity-history)

Previous page: [Choose access for a teammate](https://www.mensara.ai/how-it-works/right-access)

Next page: [Decide where your information may go](https://www.mensara.ai/how-it-works/ownership-data-flow)

Your Mensara Mind holds your team’s saved information and work.

[Join the waitlist](https://www.mensara.ai/?guide_attribution=eyJfcmFpbHMiOnsiZGF0YSI6eyJvcmlnaW5fcGF0aCI6Ii9ob3ctaXQtd29ya3MvcmVhZC1hbmQtcHJvcG9zZSIsImN0YV9pZCI6Im1hcmtkb3duIiwiY29udGVudF9yZXZpc2lvbiI6ImU2MDlmZmVhYjlhYWJiYWUifSwicHVyIjoiZ3VpZGUtY2xpY2sifX0%3D--2d0c84d035a2a7f4822144bf09006cada4f1c445#waitlist)