Product documentation
Control access to an agent
An Agent is created in either a personal or team scope. Scope determines where the Agent is listed and who can normally use or manage it.
| Scope | User-visible behavior |
|---|---|
| Personal | The Agent is listed in the personal section and is intended for its creator |
| Team | The Agent can be listed for members of the current team; creation and configuration require corresponding permission |
Choose the scope
- Start creation from the personal or team Agents section in the sidebar.
- Confirm that the creation page title matches the intended scope.
- Configure and save the Agent.
The current creation page derives scope from the entry used to start creation. It is not a general-purpose role editor.
Sessions and management
- The service controls which Agents and Sessions are returned to each user.
- A user can act on the management controls that are visible and enabled for them; the service remains the authorization boundary.
- In a shared Agent, the ability to send a message in a particular Session also depends on Session membership.
- Some spaces expose an Agent configuration as read-only.
Important limitations
- This guide does not describe role, team, or policy administration.
- Visibility in the interface is not a substitute for service-side authorization.
- Scope is not the same as an embedded publishing mode.
Errors and recovery
If an expected Agent or action is missing, verify that you are in the intended workspace and have corresponding permission. Ask the resource owner or support contact to confirm access; do not infer access from another user's screen.