Set safe boundaries

Share work without sharing everything

Sharing work in Mensara means giving the intended people a useful source and the access needed for their task. It does not require copying every related record or sharing an account. This guide explains how to prepare a handoff that another person and their agent can use while respecting separate information boundaries.

Contents

Name the shared job

Write down the result needed, what has been decided, what remains open and who is responsible next. Link to current records in a shared area the recipient may use. Label assumptions and pending approvals so the next person does not treat unfinished work as complete.

Keep shared and personal information distinct

A project decision belongs with the shared work. Your personal answer preferences and private working notes belong in their appropriate area. Do not move a protected source into a broad area simply to make a link work.

Personal zones have configured access rules. The owner can read them and can delegate some personal-zone access to admins; a “personal” label is not a promise that the workspace operator cannot access the information. Choosing access explains the combined permissions to inspect.

Check the recipient’s actual access

The recipient signs in as themselves and opens a harmless intended record. Their agent uses their access. Your successful read does not prove theirs, and a role name alone does not establish every area they can see.

If access needs changing, the owner or a properly delegated admin should use the access controls. Keep the change limited to the agreed job and inspect the resulting effective access.

A shared source, separate accounts

How does the recipient verify a handoff?

The sender prepares a handoff with the current decision, open work and source links. The recipient signs in with their own account and opens the permitted sources. Their agent uses that person’s access. If a source is excluded, the owner must correct the intended scope or supply an authorised summary; the sender’s successful read is not the recipient’s access check.

Name what each source supports, not just a folder full of files. If the recipient cannot use a source, identify the responsible person who can provide an authorised summary or adjust the intended scope. Do not guess the contents of the excluded source.

Keep actions and decisions traceable

Carry the original task, proposal or request reference into the handoff. Before repeating a save or external action, the next person should inspect its current state. Activity and history explains how evidence of the earlier work differs from the source it changed.

Related

Choose access for a teammate · Change or remove a teammate’s access · Start from what’s already decided

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.

---

# Share work without sharing everything

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

Sharing work in Mensara means giving the intended people a useful source and the access needed for their task. It does not require copying every related record or sharing an account. This guide explains how to prepare a handoff that another person and their agent can use while respecting separate information boundaries.

[Page as Markdown](https://app.mensara.ai/how-it-works/share-work.md)

[Operating procedure](https://app.mensara.ai/how-it-works/choose-access-procedure)

## Name the shared job

Write down the result needed, what has been decided, what remains open and who is responsible next. Link to current records in a shared area the recipient may use. Label assumptions and pending approvals so the next person does not treat unfinished work as complete.

## Keep shared and personal information distinct

A project decision belongs with the shared work. Your personal answer preferences and private working notes belong in their appropriate area. Do not move a protected source into a broad area simply to make a link work.

Personal zones have configured access rules. The owner can read them and can delegate some personal-zone access to admins; a “personal” label is not a promise that the workspace operator cannot access the information. [Choosing access](https://app.mensara.ai/how-it-works/right-access) explains the combined permissions to inspect.

## Check the recipient’s actual access

The recipient signs in as themselves and opens a harmless intended record. Their agent uses their access. Your successful read does not prove theirs, and a role name alone does not establish every area they can see.

If access needs changing, the owner or a properly delegated admin should use [the access controls](https://app.mensara.ai/how-it-works/change-access). Keep the change limited to the agreed job and inspect the resulting effective access.

### A shared source, separate accounts

How does the recipient verify a handoff?

The sender prepares a handoff with the current decision, open work and source links. The recipient signs in with their own account and opens the permitted sources. Their agent uses that person’s access. If a source is excluded, the owner must correct the intended scope or supply an authorised summary; the sender’s successful read is not the recipient’s access check.

## Use links that preserve context

Name what each source supports, not just a folder full of files. If the recipient cannot use a source, identify the responsible person who can provide an authorised summary or adjust the intended scope. Do not guess the contents of the excluded source.

## Keep actions and decisions traceable

Carry the original task, proposal or request reference into the handoff. Before repeating a save or external action, the next person should inspect its current state. [Activity and history](https://app.mensara.ai/how-it-works/activity-history) explains how evidence of the earlier work differs from the source it changed.

## Related

- [Choose access for a teammate](https://app.mensara.ai/how-it-works/right-access)
- [Change or remove a teammate’s access](https://app.mensara.ai/how-it-works/change-access)
- [Start from what’s already decided](https://app.mensara.ai/how-it-works/carry-context)

Previous page: [Join your team’s Mind](https://app.mensara.ai/how-it-works/join-a-team)

Next page: [Change or remove a teammate’s access](https://app.mensara.ai/how-it-works/change-access)

A teammate’s effective access is what they can actually read and do after roles, profiles, defaults and other grants are considered.

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