Build and share

Invite a teammate to your Mind

A Mensara Mind holds your team's shared information and work. Inviting a teammate gives them their own way to sign in, with access chosen for their job. Use this guide to bring one person into the right Mind and check that they can use the information they need.

Contents

How team access works

Each person uses their own account. Their role controls which administrative actions they may take: the owner controls the workspace, admins have the management rights the owner permits, and members use the information and tools they are allowed to access.

The records are grouped into areas called zones, with rules for reading and changing them. An access profile selects the shared zones a person can use. Role and profile work together, so making someone a member does not by itself describe every record they can open. Check any default access the Mind gives new members.

The invitation is only the first stage. Your teammate accepts it and signs in; then you check a useful task using their account. That check matters because sending an email does not prove the person has joined or has the intended access. Team and roles and zones and permissions explain the controls in more detail.

Diagram

Check both the role and the shared areas

A role describes management rights. A profile selects shared zones for the person’s work.

In words

Each teammate uses their own account. Their role determines the administrative actions they may take. Their access profile selects shared zones, and each zone has rules for reading and changing its records. Check default access as well as the chosen profile. A member role alone does not tell you every record the person may open. After joining, test an allowed task using their own account.

Before you start

Confirm the email address, the intended Mind and the information the person needs for their work. Use the owner account or an admin allowed to manage invitations through the account interface. Sending an invitation sends an email to that address.

Send the invitation once

The Portal is your Mind's web interface. Open it in your browser, then:

  1. Open Members and follow its account membership link.
  2. Check the current members and pending invitations.
  3. Invite the confirmed email address as a member through the supported form.
  4. Check whether the invitation was issued, was already pending or was refused.

If your connected agent has an invitation tool for this Mind, the signed-in owner may be able to use it. The tool is owner-only and is not exposed in every connection. Otherwise use the human account route above.

Check after they join

Have your teammate accept the invitation and sign in with their own invited account. Membership updates may take time to reach the Mind, so check that it recognises them before assuming access is ready.

Ask them to open a harmless record in an area intended for them and complete one useful task. Their connected agent works within that person's access. If you are testing a restriction, use a disposable test record in an excluded area, rather than sensitive content, to check that the request is refused.

Diagram

From invitation to checked access

The inviter and recipient have different steps. Check the result in the recipient’s account.

In words

The inviter confirms the Mind, address and intended access, checks existing membership and pending state, then issues one invitation. The recipient accepts and signs in with the invited account. Membership must then reach the Mind. The teammate completes an allowed task with their own account, and you check the result. An issued invitation, recognised membership and verified access are three separate observations; sending an email proves neither joining nor access.

Recognise the three results

  • Invited: the invitation was issued.
  • Joined: the person accepted it and the Mind recognises their membership.
  • Access checked: they completed an allowed task with their own account.

If access is wrong, have the owner or an admin allowed to manage access correct the profile. Do not make the person an admin simply to make a read work. Choose the right access explains that decision.

If the invitation is still pending

Check its current state before sending another invitation. If the person signed in with a different account, have them use the invited identity. Join a team gives the recipient's steps.

Removing access is a separate action through the account and Mind's supported controls. Check the resulting access; removal cannot recall an email already sent.

Related

Join your team's Mind · Give each person and their agent the right access · Team and roles · Zones and permissions

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.

---

# Invite a teammate to your Mind

Guides · Build and share · [How it works](https://app.mensara.ai/how-it-works)

A Mensara Mind holds your team's shared information and work. Inviting a teammate gives them their own way to sign in, with access chosen for their job. Use this guide to bring one person into the right Mind and check that they can use the information they need.

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

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

## How team access works

Each person uses their own account. Their **role** controls which administrative actions they may take: the owner controls the workspace, admins have the management rights the owner permits, and members use the information and tools they are allowed to access.

The records are grouped into areas called **zones**, with rules for reading and changing them. An **access profile** selects the shared zones a person can use. Role and profile work together, so making someone a member does not by itself describe every record they can open. Check any default access the Mind gives new members.

The invitation is only the first stage. Your teammate accepts it and signs in; then you check a useful task using their account. That check matters because sending an email does not prove the person has joined or has the intended access. [Team and roles](https://app.mensara.ai/how-it-works/multiplayer) and [zones and permissions](https://app.mensara.ai/how-it-works/zones-and-permissions) explain the controls in more detail.

### Check both the role and the shared areas

A role describes management rights. A profile selects shared zones for the person’s work.

#### In words

Each teammate uses their own account. Their role determines the administrative actions they may take. Their access profile selects shared zones, and each zone has rules for reading and changing its records. Check default access as well as the chosen profile. A member role alone does not tell you every record the person may open. After joining, test an allowed task using their own account.

## Before you start

Confirm the email address, the intended Mind and the information the person needs for their work. Use the owner account or an admin allowed to manage invitations through the account interface. Sending an invitation sends an email to that address.

## Send the invitation once

The **Portal** is your Mind's web interface. Open it in your browser, then:

1. Open **Members** and follow its account membership link.
2. Check the current members and pending invitations.
3. Invite the confirmed email address as a member through the supported form.
4. Check whether the invitation was issued, was already pending or was refused.

If your connected agent has an invitation tool for this Mind, the signed-in owner may be able to use it. The tool is owner-only and is not exposed in every connection. Otherwise use the human account route above.

## Check after they join

Have your teammate accept the invitation and sign in with their own invited account. Membership updates may take time to reach the Mind, so check that it recognises them before assuming access is ready.

Ask them to open a harmless record in an area intended for them and complete one useful task. Their connected agent works within that person's access. If you are testing a restriction, use a disposable test record in an excluded area, rather than sensitive content, to check that the request is refused.

### From invitation to checked access

The inviter and recipient have different steps. Check the result in the recipient’s account.

#### In words

The inviter confirms the Mind, address and intended access, checks existing membership and pending state, then issues one invitation. The recipient accepts and signs in with the invited account. Membership must then reach the Mind. The teammate completes an allowed task with their own account, and you check the result. An issued invitation, recognised membership and verified access are three separate observations; sending an email proves neither joining nor access.

## Recognise the three results

- **Invited:** the invitation was issued.
- **Joined:** the person accepted it and the Mind recognises their membership.
- **Access checked:** they completed an allowed task with their own account.

If access is wrong, have the owner or an admin allowed to manage access correct the profile. Do not make the person an admin simply to make a read work. [Choose the right access](https://app.mensara.ai/how-it-works/right-access) explains that decision.

## If the invitation is still pending

Check its current state before sending another invitation. If the person signed in with a different account, have them use the invited identity. [Join a team](https://app.mensara.ai/how-it-works/join-a-team) gives the recipient's steps.

Removing access is a separate action through the account and Mind's supported controls. Check the resulting access; removal cannot recall an email already sent.

## Related

- [Join your team's Mind](https://app.mensara.ai/how-it-works/join-a-team)
- [Give each person and their agent the right access](https://app.mensara.ai/how-it-works/right-access)
- [Team and roles](https://app.mensara.ai/how-it-works/multiplayer)
- [Zones and permissions](https://app.mensara.ai/how-it-works/zones-and-permissions)

Previous page: [Install an approved agent](https://app.mensara.ai/how-it-works/install-an-agent)

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

Use your own identity and check a permitted source.

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