Set safe boundaries

Change or remove a teammate’s access

A teammate’s effective access is what they can actually read and do after roles, profiles, defaults and other grants are considered. Changing a profile is different from removing a person from the workspace. This guide helps an owner or authorised admin make the intended change and verify its scope.

Contents

Choose the change the job requires

For a change of responsibilities, identify the areas and actions the person should retain, gain or lose. Use roles and profiles to separate management authority from information access.

A profile can extend the Everyone default or replace it, depending on its configuration. Removing an assignment does not itself prove that default, direct or group grants have gone. Likewise, Locked down does not erase every existing grant.

Inspect and update the intended account

In the Mind’s Portal, open Settings, then Members under Workspace, to reach Team access. Inspect the person’s Access profile and Effective access. The owner can manage access; an admin needs the relevant delegation. Role management is a separate delegation and does not allow changing the owner’s role or the viewer’s own role through those controls.

Choose the intended profile through the available control, then inspect the result. Check a harmless permitted task and an intended restriction using that person’s own account.

Separate a departure from a profile change

Removing membership on the account site and closing local Portal access are separate surfaces. Use the owner account and follow the supported departure process for the intended person. Do not treat a local row disappearing as proof that all credentials, model routes and memberships have been revoked everywhere.

The Portal’s Remove member flow includes a chat-history choice: Export, then delete or Delete only. Confirming it deletes that local chat history; an export must be downloaded from the result before dismissing it. Read every result shown. This is a consequential action to review with the responsible owner, not a routine substitute for changing a profile.

Follow up on partial removal

The local removal result can report that gateway-token lineage is pending account-side removal and model routes or broker-token work is unavailable from the Portal. Have the authorised owner or operator complete those named steps and confirm the final account membership and credential state. A successful local cleanup does not establish full departure completion.

Reconcile before retrying

If the connection fails, inspect the intended person’s current membership and each reported surface before repeating removal. Some cleanup may already have happened. Keep an export and the removal result with the authorised owner; never paste a token into a shared note to prove it was revoked.

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://app.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://app.mensara.ai/llms.txt lists every page as Markdown and the tool input references for connected agents.

---

# Change or remove a teammate’s access

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

[Page as Markdown](https://app.mensara.ai/how-it-works/change-access.md)

## Choose the change the job requires

For a change of responsibilities, identify the areas and actions the person should retain, gain or lose. Use [roles and profiles](https://app.mensara.ai/how-it-works/right-access#roles-and-profiles) to separate management authority from information access.

## Inspect and update the intended account

In the Mind’s Portal, open **Settings**, then **Members** under Workspace, to reach **Team access**. Inspect the person’s **Access profile** and **Effective access**. The owner can manage access; an admin needs the relevant delegation. Role management is a separate delegation and does not allow changing the owner’s role or the viewer’s own role through those controls.

Choose the intended profile through the available control, then inspect the result. Check a harmless permitted task and an intended restriction using that person’s own account.

## Separate a departure from a profile change

The Portal’s **Remove member** flow includes a chat-history choice: **Export, then delete** or **Delete only**. Confirming it deletes that local chat history; an export must be downloaded from the result before dismissing it. Read every result shown. This is a consequential action to review with the responsible owner, not a routine substitute for changing a profile.

## Follow up on partial removal

## Reconcile before retrying

## Related

- [Choose access for a teammate](https://app.mensara.ai/how-it-works/right-access)
- [Understand your Mind’s settings](https://app.mensara.ai/how-it-works/mind-settings)
- [Decide where your information may go](https://app.mensara.ai/how-it-works/ownership-data-flow)

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

Next page: [Track tasks and check their progress](https://app.mensara.ai/how-it-works/track-tasks)

A task is a saved record of work somebody has agreed to do.

[Join the waitlist](https://app.mensara.ai/#waitlist)