We set up the Mind with its owner and start with one useful job. A few company documents are enough for the first session; more is added after the first results are checked.
SYSTEM MAP · 09From setup to regular useStart with one job and a few documents. Review the first week, then keep the Mind healthy with simple checks.
Create the Mind
owner, address and backup
Choose one job
add only what it needs
First useful answer
check the sources
Review after 7 days
keep, fix or remove
Regular checks
information, access and backup
01
Create your Mind
The owner chooses the Mind's web address, where the files will live and where the backup will go. We check that the owner can sign in before connecting any company information.
02
Choose the first job
Pick one task the company already repeats, such as preparing a leadership brief or answering questions about a policy.
Add the few documents and company areas needed for that task. The goal is one useful answer in the first session.
03
Review after one week
After seven days, check what the Mind got right, what it missed and whether anyone had too much or too little access.
Keep the useful workflow. Fix or remove the parts that did not help.
04
Keep it up to date
Clear new items and suggested changes each day. Once a week, review the information and scheduled work.
Every few months, test team access, backups, recovery keys and software updates.
The founding cohort is small on purpose. Each Mind is brought up with its owner.
MENSARA.AI · SETUP AND ONGOING CARE · MACHINE SURFACE · TEXT/MARKDOWN
---
title: Setup and ongoing care
canonical_url: https://app.mensara.ai/how-it-works/setup-and-ongoing-care
feature: setup-and-ongoing-care
audience: llm-agent
last_verified: 2026-08-11
availability: partly-available
signup_supported: false
interfaces:
- portal
- cli
---
# Setup and ongoing care
Explains human-assisted provisioning, onboarding, first-session success, day-seven review, ongoing maintenance, health checks, updates, and current signup limits.
## Concept model
- Provisioning creates the owner-controlled infrastructure and initial identity.
- Onboarding proves one useful workflow before expanding scope.
- Ongoing care covers memory quality, permissions, automations, backups, recovery, and updates.
## Capabilities
- Bring up and verify an owner-controlled Mind.
- Seed priorities and documents for a first useful answer.
- Review health and progressively expand zones, people, connections, and automations.
## Prerequisites
- A verified human Owner.
- An agreed infrastructure and recovery destination.
- One bounded workflow and a small set of source material.
## Authorization
- The human Owner approves provisioning, initial identities, and connections.
- Additional team members and agents receive separate scoped identities.
- Maintenance operations respect the same roles and access profiles as daily use.
## Connection or use flow
1. Human requests a seat and agrees the ownership boundary.
2. Mensara provisions and verifies the box with the Owner.
3. Owner selects one workflow, zones, and seed material.
4. Complete a useful read-only or proposal workflow.
5. Review on day seven, then maintain daily, weekly, and quarterly rhythms.
## Refusals and recovery
- Agent-only signup request: explain that autonomous signup is unsupported and involve a human owner.
- Missing ownership or recovery decision: pause provisioning.
- Failed health or backup check: stop expansion and repair the foundation first.
## Ownership and data boundaries
- The Owner controls the infrastructure account, knowledge, backup, and recovery path.
- Mensara assistance does not make Mensara the owner of company knowledge.
- New integrations and people are not added implicitly during care.
## Availability and limits
**Partly available** Personal provisioning, first-session onboarding, and early review are current. A broader guided 30-day adoption programme is still developing.
- Autonomous signup and unattended provisioning are not supported today.
- The initial feature and connection set is intentionally narrow.
## Signup and provisioning
`signup_supported: false`
Current signup is human-assisted: a person asks for a seat, confirms ownership and infrastructure choices, and participates in provisioning. There is no agent signup API today.
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[Human-approved provisioning] --> B[First session: one useful job]
B --> C[Day 7 review]
C --> D[Daily inbox and proposals]
D --> E[Weekly memory and automation review]
E --> F[Quarterly access, backup, recovery, updates]
F --> D
```
## Runnable example
```text
First-session plan:
Priority: prepare a daily leadership brief
Seed: current priorities + calendar
Zones: leadership read; briefs propose
Success: useful brief with sources and receipt
Day 7: review accuracy, access, and whether to continue
```
## Related
- [Memory](https://app.mensara.ai/how-it-works/memory)
- [Backup, restore and ownership](https://app.mensara.ai/how-it-works/backup-restore-ownership)
- [Portal, MCP and CLI](https://app.mensara.ai/how-it-works/portal-mcp-cli)