Keep related records together
Your Mind holds saved records, such as a decision, a customer note or a way of working. Zones give those records boundaries that can be checked when someone or their agent asks to use them. How memory works explains the saved information and its history.
For example, a team might separate ordinary company information from payroll or hiring records. That is an illustrative arrangement, not a default structure every Mind has. Choose areas around the work and the people who need the information.
Use each person’s own identity
Every teammate signs in with their own account. Their connected agent works using that person’s access. A well-written prompt cannot give it permission to open an excluded area.
That is why inviting a teammate includes checking a task using the teammate’s account. A successful read by the owner does not establish what the teammate can read.
Separate reading, suggesting and approving
Reading lets someone use the records in an area. Proposing lets them suggest changes. Approval authority lets an authorised reviewer decide a request of the relevant kind. Those are different permissions; being able to read a policy does not automatically let you replace or approve it.
The owner can group access into a profile, a named selection of shared areas for a job. A person’s role, profile, default access and any other grants all matter. Choose access for a teammate explains how to check the combined result.
An agent uses the access of its person
A connected agent does not get a separate pass into excluded areas.
The Mind identifies the person behind the request and checks their effective access for the requested area and action. An allowed read can return the record. An excluded read is refused or left out of discovery. Permission to read does not itself grant permission to suggest or approve a change.
Understand what a permission check changes
The Mind checks the caller’s permissions before serving a read or allowing a change. Search results omit areas the caller cannot read. A direct request for an excluded record is refused; the agent must not fill the gap by guessing what it contains.
Write permission and immediate saving are also different questions. A permitted suggestion can still wait for review because of the Mind’s settings and checks. Read the returned outcome before reporting that a record changed.
Check the boundaries with harmless information
Agree one record the person should be able to use and, where you are testing a restriction, a disposable record in an area they should not be able to open. Use their own account for the check. Confirm both the useful task and the intended refusal.
If access is wrong, ask the owner or an admin allowed to manage access to inspect the assignments. Do not make someone an admin merely to make one read work. The access guide gives the review steps.
When an area is missing
A missing search result can mean the record is absent, you lack access, or the question did not find it. Ask the agent to identify which part it can establish and open the sources it used.
If you need access for a real job, tell the owner which information and action the job requires. They can review the scope without sharing the protected contents in the request itself.
Related
Practical guides for people and agents