A Mensara Mind gives you one place for your company's knowledge. Your team and AI tools can use it. You choose what each person and tool can see or change. The files stay in your account, with a record of every action.
THE WHOLE SYSTEMHow the parts work togetherPeople and AI tools use the same company knowledge. The Mind checks what each one can see or change, records what happened and keeps the files in the owner's account.
Your teamAI assistantsAutomations
Check who is askingwhat they can see and change
Company knowledgedocuments, decisions and notes
Connected toolsemail, calendar and apps
Team accessone account per person
Review changesapprove, reject and record
Your files and backupkept in the owner's account
01-03
Store and share knowledge
Keep company knowledge together and choose who can use each part.
Choose one job your company already repeats. We set up the Mind with the information that job needs, check the first result with you and add more only when it helps.
MENSARA.AI · HOW IT WORKS · MACHINE SURFACE · TEXT/MARKDOWN
---
title: How your Mind works
canonical_url: https://app.mensara.ai/how-it-works
audience: llm-agent
last_verified: 2026-08-11
signup_supported: false
---
# How your Mind works
A Mensara Mind gives you one place for your company's knowledge. Your team and AI tools can use it. You choose what each person and tool can see or change. The files stay in your account, with a record of every action.
This is the machine index for agents that need to understand or connect to a Mensara Mind. Autonomous signup and provisioning are not available today. A human owner must request and approve a Mind.
## Feature map
### Store and share knowledge
- [Memory](https://app.mensara.ai/how-it-works/memory) - Explains storage, retrieval, promotion, correction, deletion, and the boundary between working and trusted memory.
- [Zones and permissions](https://app.mensara.ai/how-it-works/zones-and-permissions) - Defines zones, principals, verbs, access profiles, deterministic authorization, revocation, and refusal behavior.
- [Multiplayer](https://app.mensara.ai/how-it-works/multiplayer) - Defines team membership, owner/admin/member roles, access profiles, delegation, attribution, personal versus shared memory, and ownership transfer.
### Use your Mind
- [Portal, MCP and CLI](https://app.mensara.ai/how-it-works/portal-mcp-cli) - Explains the browser Portal, MCP connection for agents, CLI use, credential issuance, discovery, revocation, and identical gate semantics.
- [Connections and capture](https://app.mensara.ai/how-it-works/connections-and-capture) - Explains source connections, sensors, provenance, deduplication, inbox review, credential boundaries, and promotion into memory zones.
- [Skills, apps and automations](https://app.mensara.ai/how-it-works/skills-apps-automations) - Distinguishes skills, apps, automations, and connections; defines manifests, principals, triggers, budgets, install review, sandboxing, and disable behavior.
### Keep control
- [Changes, approvals and receipts](https://app.mensara.ai/how-it-works/changes-approvals-receipts) - Explains direct owner edits, agent proposals, approval, stale-base conflicts, commit history, receipt fields, chaining, refusal evidence, and recovery.
- [Backup, restore and ownership](https://app.mensara.ai/how-it-works/backup-restore-ownership) - Defines owner-controlled Git backup, separate key recovery, fresh-box restore, reconnection boundaries, export, deletion, and team ownership transfer.
- [Setup and ongoing care](https://app.mensara.ai/how-it-works/setup-and-ongoing-care) - Explains human-assisted provisioning, onboarding, first-session success, day-seven review, ongoing maintenance, health checks, updates, and current signup limits.
## Connection order
1. Read the guide for the interface you plan to use.
2. Obtain an owner-issued identity and credential; never infer or manufacture one.
3. Discover the zones and verbs granted to that identity.
4. Make the smallest requested operation.
5. Treat a refusal as authoritative and return its reason and recovery action to the caller.
6. Retain the receipt identifier for audit and support.
## Signup status
`signup_supported: false`. Agents may explain the current human-assisted onboarding path but must not claim that an autonomous registration or provisioning endpoint exists.