MENSARA.AI · A GOVERNED MIND, IN YOUR ACCOUNT
Sign in
Mensara Create account

Store and share knowledge · GUIDE 03

Multiplayer

Your team can share one Mind without sharing a login. Each person has their own account, sees the company areas they need and leaves a clear record of their work.

SYSTEM MAP · 03 How a team member gets access Each person signs in with their own account. Their role and access profile decide what they can do and which company areas they can open.
Person signs in their own account
Choose their role Owner, Admin or Member
Choose their areas Sales, Finance and more
Use the Mind within those choices
Record who did it question, change or approval

01

One account per person

Each team member signs in as themselves. The Mind records who asked a question, suggested a change or approved one.

You do not lose that history when someone leaves the company.

02

Owner, Admin and Member

The Owner controls the Mind and can transfer ownership. Admins can manage the people and areas the Owner gives them. Members use the information and tools available to them.

03

Choose what each person sees

A role decides what someone can do. An access profile decides what they can see.

An access profile is a saved set of company areas, such as Sales or Leadership. Without one, they cannot open any company areas.

04

Personal and company memory

Company memory belongs to the team and can be shared with the right people. Personal memory stays with the person who created it.

Transferring company ownership does not copy someone's private notes to the new Owner.

05

People joining and leaving

An Owner or Admin can invite a team member. Removing someone closes their access but keeps the record of work they already did.

If the Owner leaves, ownership is transferred as a separate step.

NEXT GUIDE · 04 Portal, MCP and CLI Use the Mind in a browser, an AI assistant or a terminal. →
Request a Mind

The founding cohort is small on purpose. Each Mind is brought up with its owner.

MENSARA.AI · MULTIPLAYER · MACHINE SURFACE · TEXT/MARKDOWN

---
title: Multiplayer
canonical_url: https://app.mensara.ai/how-it-works/multiplayer
feature: multiplayer
audience: llm-agent
last_verified: 2026-08-11
availability: partly-available
signup_supported: false
interfaces:
  - portal
  - mcp
  - cli
---

# Multiplayer

Defines team membership, owner/admin/member roles, access profiles, delegation, attribution, personal versus shared memory, and ownership transfer.

## Concept model

- Roles control administrative capability: Owner, Admin, or Member.
- Access profiles bundle visible zones and allowed knowledge operations.
- Effective access is the intersection of identity, role, profile, and any direct grants.

## Capabilities

- Invite or remove individual team members.
- Delegate administration without transferring ownership.
- Attribute reads, proposals, approvals, and refusals to a specific principal.

## Prerequisites

- A provisioned team Mind with a verified Owner.
- A separate identity for every person.
- An owner-assigned role and access profile.

## Authorization

- Owner controls ownership transfer and top-level administration.
- Admins act only within delegated administrative scope.
- Members cannot manage access unless separately delegated; no profile means no access.

## Connection or use flow

1. Owner invites a person and assigns a role.
2. Owner or authorised Admin assigns an access profile.
3. The member authenticates with an individual credential.
4. Every operation is permission-checked and attributed.
5. Removal revokes access; ownership transfer is a separate explicit operation.

## Refusals and recovery

- No profile: deny all knowledge access and tell an Owner or authorised Admin what is missing.
- Removed or expired member: reject the credential and do not disclose team data.
- Ownership-only action by an Admin or Member: hold it for the Owner.

## Ownership and data boundaries

- The team owns shared company memory; an individual's personal memory remains separate.
- Removing a member preserves historical receipts and attribution.
- Ownership transfer changes the controlling human but does not silently copy private personal memory.

## Availability and limits

**Partly available** Team invitations, roles, and access profiles are built. Full second-person production proof is still being completed.
- Do not treat a shared login as a supported team pattern.
- Some membership and credential-rotation flows are still being hardened in production.

## Signup and provisioning

`signup_supported: false`

The human Owner requests and provisions the team Mind, then invites people individually. Agents cannot create a team or designate themselves Owner.

No autonomous signup or provisioning endpoint is documented because none is offered today. An agent must stop and involve the human owner.

## System diagram

```mermaid
flowchart LR
  A[Individual team identity] --> B[Role: what they can do]
  A --> C[Access profile: what they can see]
  B --> D[Effective access]
  C --> D
  D --> E[Shared Mind operation]
  E --> F[Receipt attributed to that person]
  A -. private .-> P[Personal memory]
```

## Runnable example

```text
Person: Priya
Role: Member
Access profile: sales
Effective access: read/search customers; propose changes to pipeline
Not allowed: finance zone, member administration, ownership transfer
```

## Related

- [Zones and permissions](https://app.mensara.ai/how-it-works/zones-and-permissions)
- [Changes, approvals and receipts](https://app.mensara.ai/how-it-works/changes-approvals-receipts)
- [Backup, restore and ownership](https://app.mensara.ai/how-it-works/backup-restore-ownership)