Who can use an assistant
Individual, group, and team assistants, members and managers, and how to turn an individual assistant into one your colleagues can use.
Every assistant is one of three kinds. You choose the kind when you create it, and it never changes.
| Kind | Who uses it | Use it when |
|---|---|---|
| Individual assistant | Just you | You are trying out a setup, or the work is yours alone |
| Group assistant | The people you add | A named group should share one assistant and what it learns |
| Team assistant | Everyone in the organization | Anyone here should be able to use it |
Anyone who can build assistants can create an individual or group assistant. Only an Owner or Admin can create a team assistant.
The app and API call the saved assistant an agent. Through the API the
kinds are the visibility values private, restricted, and
organization. Send one when you create the agent; changing it later is
refused with 409.
Why the kind is fixed
An assistant gathers things as people use it: chats, files, what it remembers for the group, and accounts granted to it. If the kind could change, every one of those would need a decision about who may now read it. Fixing the kind means nobody faces that question. To share an individual assistant, you make a team version of it.
Make a team version
Suppose Dana built Scout as an individual assistant and her team wants it.
- Open Build > Agents, then choose Scout.
- Open the actions menu and choose Make a team version.
- Name it, choose Group assistant and add its members, or choose Team assistant if you are an Admin.
- Pick any of Scout's files to copy into Company files, then click Make team version.
The new assistant gets Scout's instructions, model and model settings, tools, and memory and conversation settings, plus each skill everyone it is for can use. Dana's chats with Scout, what Scout remembers, accounts in Dana's own name, routines, chat apps, and inbox stay with Scout, which does not change.
When an Admin makes the team version, it also gets Scout's company accounts. Afterwards, Mobius lists what was left behind: skills only Dana can use, and company accounts an Admin needs to grant.
Group assistants: members and managers
Being a member of a group assistant is access to it. Members can use it, read its chats that are shared with everyone who uses it, open its files, see what it remembers for the group, and use the company accounts granted to it. Every member can see who else is in the group. Members are people; an assistant is never a member.
The person who creates a group assistant is its first manager. A manager who can build can edit its setup, add and remove members, make other members managers, correct what it remembers for the group, and delete it. Owners and Admins can do the same.
Manage members on the assistant's Configure page, in the card that shows who it is for.
- Add asks who to add and tells you what they get: everything the group shares, meaning chats shared with everyone who uses Scout, what Scout remembers for the group, its files, and the company accounts granted to it, including what was there before they joined.
- Remove tells you what the person loses. They lose the assistant, its chats and files, and what it remembers for the group at once, including chats someone shared with them by name. Their own routines on it pause and their own accounts stop working through it. A routine run already under way is not stopped. Their private chats with it are kept and nobody can open them; adding them back restores them.
- Any member can Leave.
- A group assistant always has a member. Removing the last one is refused; delete the assistant instead.
Share a chat
Your chats with an assistant start private. From the chat's menu you choose who else can read it:
| Choice | Who can read |
|---|---|
| Just me | Only you |
| Specific people… | The people you name. On a group assistant, only its members |
| Everyone who uses Scout | On a group assistant, its current members; on a team assistant, the organization |
An individual assistant has no other users, so its last choice reads Everyone in Northwind. A shared chat is read-only for everyone but you. When someone leaves a group, they stop being able to read its chats.
What stays separate
Everyone who uses an assistant gets the same instructions, model, tools, skills, and shared knowledge. Each person's own work stays theirs:
- each person's chats are their own unless they share them;
- each person's private memory stays with them, and nobody else reads it, Admins included;
- control of a connected account follows the account, not the assistant; and
- using an assistant does not grant permission to edit it.
Slack, email, Telegram, and embedded software need a reliable mapping from the outside sender to a person in Mobius before they can reach an assistant. See agent messaging.
For the permission model, read organizations and access. For what happens to personal and company work when someone leaves, read your work and the team's work.