Who can use an assistant

An assistant's audience names the people in your organization who may reach it. It is how Northwind can give Scout to the operations team without making every employee recreate Scout or see the team's shared knowledge.

The app and API call the saved assistant an agent. Under Who this agent is for, the app offers:

Choice	Use it when
Just me	One person is still testing the setup or needs a personal assistant
Only listed people	A named group should use the same assistant and shared knowledge
Everyone in the org	The assistant is suitable for any organization member with permission to use it

Start with Just me. The app creates new assistants with that choice. The employee create API also defaults to private if visibility is omitted, but an API client should send private, restricted, or organization explicitly so the intended audience survives a change in client or context.

Audience is one access decision

Being listed in an audience does not grant every kind of access. Mobius checks these questions separately:

Question	What answers it
Is this person a member of the organization?	Organization membership
May they reach this assistant at all?	The assistant audience
May they start work with it?	The organization permission to use resources
May they inspect its saved configuration?	The organization permission to view resources, plus audience reach
May they edit it or publish it more widely?	Build or administration permission, plus the assistant's ownership and audience posture

A colleague can therefore use Scout without gaining permission to edit its instructions. A person outside Scout's audience cannot discover it merely because they can use other assistants. Organization administration also does not create ordinary reach into a private assistant.

The account behind a tool has its own controls. Scout's audience does not give every Scout user control of a connected mailbox, permission to act as its owner, or permission to deliver mailbox results to the group. Connect accounts and set access covers those decisions.

Set the audience in the app

Making an assistant available beyond one person requires organization administration in the current app.

1. Open Build > Agents, then choose the assistant.
2. On Configure, click Edit.
3. Under Who this agent is for, choose Just me, Only listed people, or Everyone in the org.
4. For Only listed people, add each intended person.
5. Click Save.
6. Review the audience preview and confirm the change.

The saved card shows the audience. For a listed audience, a person who may manage it can inspect the member list. Other members receive the count rather than a directory of names.

Through the API, visibility uses the values private, restricted, and organization. Restricted and private audiences use the members subresource under /v1/agents/{id}/members. Use the interactive API reference for the request shapes.

What sharing makes common

Everyone in the audience uses the same saved instructions, model default, tools, skills, and deliberately shared knowledge. A new group member can read the knowledge already shared with that group, so check it before adding someone.

Private work stays separate:

• each person starts their own conversation and sees only the conversations allowed by that conversation's ownership;
• personal memory stays with that person;
• connected-account control and result access follow the connection, not the assistant audience; and
• audience membership alone does not reveal the saved configuration or grant edit rights.

If Maya and Jordan both use Scout, they receive the same maintained behavior. Jordan does not inherit Maya's messages, and Maya does not receive Jordan's reply unless Jordan deliberately shares it through another resource or destination.

Review a wider audience carefully

Moving from Just me to Only listed people, or from a listed group to Everyone in the org, makes Scout's shared knowledge available to more people. The app previews how many shared entries and attached resources the change affects. Answer every resource decision before you confirm.

Narrowing the audience removes future reach, but it cannot make someone forget information they already read. It may also affect conversations, private memory, routines, or grants attached to people outside the new audience. Read the preview instead of treating the audience as a cosmetic label.

Use assistants in other channels

Slack, email, Telegram, and embedded software need a reliable mapping from the outside sender to a Mobius principal. The assistant audience is still checked, along with the channel binding, the account grant, and the allowed result audience. A message arriving through another channel is not a shortcut around membership.

See agent messaging before making a shared assistant reachable outside the app.

Decide who can improve Scout

Most colleagues only need to use Scout and report what went wrong. Give edit access to the people who maintain its job, accounts, and tests. They can update the saved definition and check the same sample again without asking every user to replace a prompt.

For the permission model, read organizations and access. For what happens to personal and company work during a handoff, read your work and the team's work.