Set safe boundaries

Join your team’s Mind

Your team’s Mind is its shared collection of information and work in Mensara. An invitation lets you join with your own account and use the areas you have been given access to. This guide takes you through accepting the invitation, connecting your chosen tool and checking one useful record.

Content updated 29 October 2026.

Contents

Accept the invitation as yourself

Use the invitation addressed to you and sign in with that same email address. Enter the intended team and Mind. An invitation being sent is different from your account having joined; if the link cannot be used, ask the owner to check its state before sending another.

Use your own account rather than a colleague’s login. Your role and access follow your identity.

Check the intended area

Ask the owner which area is meant for your first task. An area of records is called a zone. Joining does not mean you can see every zone. In a Mind that started as Open team, you begin with read and suggest access to the shared areas in the default Everyone profile, such as areas, decisions, people and world-model, and no access to other people’s personal areas; an owner who has chosen Locked down removes that default. Roles and effective access explains what contributes to the permissions you actually receive.

If you have just joined but access has not appeared, the owner should check membership recognition and the intended profile before broadening permissions.

Connect your chosen tool

The Portal is your Mind’s web interface. Use its Apps & Tools connection guide if you want to work through your own AI tool. Follow connecting to the Mind, sign in as yourself and verify the identity and scope returned by the connection.

Using chat in the Portal is a separate option. Its model access can require a personal connection or one shared with you by the owner.

Try one permitted task

Open a harmless record in the intended area and ask one useful question about it. Read the source behind the answer. That observation checks your actual access; the owner successfully opening the same record does not.

If something is refused, report the Mind, account, area and action involved without copying protected content into another chat. Have the authorised owner correct the intended scope and repeat the harmless check.

Start your own working context

A teammate’s first setup can focus on their role and the information they need. Keep personal answer preferences separate from shared company policy. Carrying context forward explains how later conversations can use saved information.

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.

---

# Join your team’s Mind

Content updated 29 October 2026.

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

[Page as Markdown](https://www.mensara.ai/how-it-works/join-a-team.md)

## Accept the invitation as yourself

Use your own account rather than a colleague’s login. Your role and access follow your identity.

## Check the intended area

Ask the owner which area is meant for your first task. An area of records is called a zone. Joining does not mean you can see every zone. In a Mind that started as Open team, you begin with read and suggest access to the shared areas in the default Everyone profile, such as areas, decisions, people and world-model, and no access to other people’s personal areas; an owner who has chosen Locked down removes that default. [Roles and effective access](https://www.mensara.ai/how-it-works/right-access#roles-and-profiles) explains what contributes to the permissions you actually receive.

If you have just joined but access has not appeared, the owner should check membership recognition and the intended profile before broadening permissions.

## Connect your chosen tool

The Portal is your Mind’s web interface. Use its **Apps & Tools** connection guide if you want to work through your own AI tool. Follow [connecting to the Mind](https://www.mensara.ai/how-it-works/portal-mcp-cli), sign in as yourself and verify the identity and scope returned by the connection.

Using [chat in the Portal](https://www.mensara.ai/how-it-works/use-chat) is a separate option. Its model access can require a personal connection or one shared with you by the owner.

## Try one permitted task

## Start your own working context

A teammate’s first setup can focus on their role and the information they need. Keep personal answer preferences separate from shared company policy. [Carrying context forward](https://www.mensara.ai/how-it-works/carry-context) explains how later conversations can use saved information.

## Related

- [Portal, MCP and CLI](https://www.mensara.ai/how-it-works/portal-mcp-cli)
- [Ask your first question](https://www.mensara.ai/how-it-works/first-useful-question)
- [Choose access for a teammate](https://www.mensara.ai/how-it-works/right-access)

Previous page: [Invite a teammate to your Mind](https://www.mensara.ai/how-it-works/invite-a-teammate)

Next page: [Share work without sharing everything](https://www.mensara.ai/how-it-works/share-work)

Sharing work in Mensara means giving the intended people a useful source and the access needed for their task.

[Join the waitlist](https://www.mensara.ai/?guide_attribution=eyJfcmFpbHMiOnsiZGF0YSI6eyJvcmlnaW5fcGF0aCI6Ii9ob3ctaXQtd29ya3Mvam9pbi1hLXRlYW0iLCJjdGFfaWQiOiJtYXJrZG93biIsImNvbnRlbnRfcmV2aXNpb24iOiIzMzZmMjI3YzhmMmViMjczIn0sInB1ciI6Imd1aWRlLWNsaWNrIn19--501263fc2ccadeb1293dc8bc3befe1a294030c32#waitlist)