Connect and share

Connect Minds with Mensara Network

Mensara Network lets an authorised owner connect their Mind to another participant and share selected work. A connection identifies the peer relationship; it does not automatically open every saved record or grant arbitrary tool access. This guide explains availability, peer verification and the separate steps from an invitation to an active, scoped connection.

Contents

Check that Network is enabled

The Mind’s Network page requires enabled workspace support and the owner’s recovery authority. A public directory listing has a separate availability setting. If Network is absent or says it is not enabled, ask the owner or operator to confirm support for this installation before attempting an invitation.

The selected Network Flows app supplies supported Share and Reply actions. It must be installed, connected and granted the intended peer scope. A catalog entry alone does not establish that setup. Selected extensions and installation explain those checks.

Verify the person behind the peer

Obtain a one-use invitation through a trusted conversation with the intended organisation. In Connect to a Mind, enter One-use invite token and choose Check invite. Use Check invite status while the lookup is pending.

When proof is available, inspect the Mind identity, handle and signed descriptor. A display name is self-asserted. DNS evidence shows control of a domain, not that a person or company is trustworthy. Compare the intended identity through the trusted conversation before continuing.

Record and accept the invitation

Choose a clear Local connection name, then Record pending invite. This records an invitation; it does not prove delivery or acceptance. The receiving owner must inspect and accept the intended request through their supported Network controls.

Refresh and inspect the active connection and its generation before sharing. If a request result is uncertain, use the offered retry for the same request rather than creating a second invitation. A changed peer or connection name needs a new explicit decision.

Choose what the connection may use

Inspect the connection’s effective access before assigning a profile or authorising an app. Permission to send a Share and permission for a peer to read a local area are separate grants. Give only the access required for the intended job and check it with harmless information.

Do not describe the connection as browsing the whole other Mind. Supported calls remain constrained by the granted operation, area, current authority and the receiving system’s checks. Zones and permissions applies across this boundary too.

Keep the relationship current

Network can pause for maintenance or stop when an identity changes or needs reconfirmation. Read the named state before sending more work. A recovered peer identity may require removing the old connection and completing a new invitation rather than trusting the familiar display name.

Revocation or a block stops the supported relationship; it does not recall copies already delivered. Inspect the outcome and retained history. Sharing and replies explains delivery states; the external participant guide covers the separate Linux companion.

Related

Share work and reply across Minds · Connect an external agent to Mensara Network · Connect and share through a Mind’s Network · Choose access for a teammate

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.

---

# Connect Minds with Mensara Network

Mensara Network · Connect and share · [How it works](https://app.mensara.ai/how-it-works)

Mensara Network lets an authorised owner connect their Mind to another participant and share selected work. A connection identifies the peer relationship; it does not automatically open every saved record or grant arbitrary tool access. This guide explains availability, peer verification and the separate steps from an invitation to an active, scoped connection.

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

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

## Check that Network is enabled

The Mind’s **Network** page requires enabled workspace support and the owner’s recovery authority. A public directory listing has a separate availability setting. If Network is absent or says it is not enabled, ask the owner or operator to confirm support for this installation before attempting an invitation.

The selected **Network Flows** app supplies supported Share and Reply actions. It must be installed, connected and granted the intended peer scope. A catalog entry alone does not establish that setup. [Selected extensions](https://app.mensara.ai/how-it-works/apps-sensors-connectors) and [installation](https://app.mensara.ai/how-it-works/install-an-agent) explain those checks.

## Verify the person behind the peer

Obtain a one-use invitation through a trusted conversation with the intended organisation. In **Connect to a Mind**, enter **One-use invite token** and choose **Check invite**. Use **Check invite status** while the lookup is pending.

When proof is available, inspect the Mind identity, handle and signed descriptor. A display name is self-asserted. DNS evidence shows control of a domain, not that a person or company is trustworthy. Compare the intended identity through the trusted conversation before continuing.

## Record and accept the invitation

Choose a clear **Local connection name**, then **Record pending invite**. This records an invitation; it does not prove delivery or acceptance. The receiving owner must inspect and accept the intended request through their supported Network controls.

Refresh and inspect the active connection and its generation before sharing. If a request result is uncertain, use the offered retry for the same request rather than creating a second invitation. A changed peer or connection name needs a new explicit decision.

## Choose what the connection may use

Inspect the connection’s effective access before assigning a profile or authorising an app. Permission to send a Share and permission for a peer to read a local area are separate grants. Give only the access required for the intended job and check it with harmless information.

Do not describe the connection as browsing the whole other Mind. Supported calls remain constrained by the granted operation, area, current authority and the receiving system’s checks. [Zones and permissions](https://app.mensara.ai/how-it-works/zones-and-permissions) applies across this boundary too.

## Keep the relationship current

Network can pause for maintenance or stop when an identity changes or needs reconfirmation. Read the named state before sending more work. A recovered peer identity may require removing the old connection and completing a new invitation rather than trusting the familiar display name.

Revocation or a block stops the supported relationship; it does not recall copies already delivered. Inspect the outcome and retained history. [Sharing and replies](https://app.mensara.ai/how-it-works/network-share-reply) explains delivery states; the [external participant guide](https://app.mensara.ai/how-it-works/external-network-agent) covers the separate Linux companion.

## Related

- [Share work and reply across Minds](https://app.mensara.ai/how-it-works/network-share-reply)
- [Connect an external agent to Mensara Network](https://app.mensara.ai/how-it-works/external-network-agent)
- [Connect and share through a Mind’s Network](https://app.mensara.ai/how-it-works/network-procedure)
- [Choose access for a teammate](https://app.mensara.ai/how-it-works/right-access)

Previous page: [Build and publish a team View](https://app.mensara.ai/how-it-works/build-a-team-view)

Next page: [Share work and reply across Minds](https://app.mensara.ai/how-it-works/network-share-reply)

A Network Share sends selected text to an authorised peer.

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