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. When you accept a connection, Mensara applies safe defaults unless the Network defaults setting is off. The peer can send material that is held for your review, and it can read the connection’s own folder under Connections. Your installed apps may also get permission to send to that peer. Defaults are applied once, at acceptance, and your later edits are kept. Check what was applied before relying on it.
A Share is not a private draft. Each Share you queue is saved in full in that connection’s folder, and the connected Mind can read that copy. Treat sending a Share as disclosing its exact text to that Mind. Sending also needs the peer to be able to read that folder, so with the defaults off a Share is refused until you grant that read. Reading other areas of your Mind is a separate grant. 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
Practical guides for people and agents