Agent Sharing & Access
Two owner-only surfaces on the Agent Detail page control who can reach an agent: Settings › People (the former Access tab) manages the people the agent is shared with (they use it in the Workspace), and the Channels tab manages external clients (outside users reaching the agent through Slack, Telegram, WhatsApp, voice calls, or public links).
Concepts
operator or above. Operators log into the Trinity UI and get interact-level access to agents shared with them. A platform account with role user works in the Workspace only — see Roles and Permissions.Settings › People — Trinity Operators
Settings › People lists the people this agent is shared with. It is the Access tab moved into the Settings home, unchanged.
Open the agent detail page, click the Settings tab and pick People in the rail (owner only; ?tab=settings§ion=people, and an old ?tab=access link lands there too).
Enter an email and click Add person. As you type, the field suggests people who already have an account on this instance, by email, username or name; pick one, or type any address. The person can sign in to the Workspace with a code emailed to them. Sharing does not create a platform account or add the email to the login whitelist; whether someone also gets the operator UI is their platform role, which an admin sets on the person's row here or in Settings → Access.
- • Active — the email resolved to an existing Trinity account (shows username, role, and last-active time, or "never signed in"). An admin may see a role select on the row instead of the role label: the role applies on every agent, every change asks for confirmation, and an admin's own row stays read-only.
- • Pending — no platform account ("No platform account — uses the Workspace"). Where the row offers Give a platform account, an admin can create the account right away (after a confirmation; as
user— Workspace only — unless an earlier allow-list entry set another role), so the person can be assigned to the agent before they first sign in; they sign in at/login. Give accounts to colleagues — a platform account sees the team's view of every agent shared with its address — and keep outside clients on a plain share.
Each operator row also carries a proactive-messaging toggle — "allow this operator to receive proactive DMs from the agent." It is off by default; turn it on per operator to let the agent message that person unprompted. This is a per-recipient DM permission (PUT /api/agents/{name}/shares/proactive, body {email, allow_proactive}). Trinity records consent in three states — not asked (every new share), declined and consented — and only consented lets the agent send; the other two are both a no, kept apart so you can see whether anyone ever asked.
Click Remove on a row to revoke access.
When you add someone with no account, Trinity emails them an invitation that says who invited them and which agent, and links to the Workspace sign-in. Use Resend inviteon their Pending row to send it again, up to 3 times an hour. If email isn't set up for sign-in on your instance, no invitation goes out and the panel says so, so tell them how to sign in yourself.
The invitation's link is built from FRONTEND_URL (in .env) only. If FRONTEND_URL is empty, the email carries no link and tells the person to use your Trinity sign-in page. The Public URL is never used for invitations, because the public chat address serves chat only and would answer the Workspace with an error. Set FRONTEND_URL whenever you set a Public URL.
On instances licensed for it, Settings › People also shows a People this agent serves section above this list: the agent's primary person, its other stakeholders, and the seat the agent holds or serves. Assigning someone there also shares the agent with them, because an assignment by itself grants no access; a row for someone the agent is not shared with carries a warning and Share with them. Without the entitlement the section is absent, and non-admins see it read-only.
The per-recipient DM toggle above is complemented on the channel side by the per-channel Slack consent — see Slack Integration. Platform-wide proactive-messaging rate caps are admin-configurable in Settings.
Access Levels
| Level | Permissions |
|---|---|
| Owner | Full control — create, delete, configure, share, manage credentials and schedules. |
| Shared operator | Interact only — chat, run tasks, start and stop the agent, view files (except credential files) and the executions they started. Cannot modify config, credentials, or permissions. |
| Admin | Full access to all agents regardless of ownership. |
What someone you share an agent with can do
.env, .mcp.json, SSH and cloud credentials, key and certificate files (*.key, *.pem, *.p12, *.pfx) and the agent runtimes' login files. Trying shows a message saying so.What the agent does for someone you share it with
An agent acts for whoever is chatting with it, so Trinity holds the agent to that person's limits for the length of their turn. Trinity decides this from the execution record, not from anything the person or the agent says:
When the agent refuses something for these reasons it says so, so the person can ask the owner. A turn the platform starts to continue earlier work (for example the agent waking up when an ask it raised is answered, or when a delegated run finishes) is held to the same limits as the turn it continues. If the person who answered an ask could not stand as the asking turn (a shared person answering the owner's ask, say), the wake-up is held to a shared person's limits.
Enforcement notes:
Channels Tab — External Clients
The Channelstab is organized around "who outside the team can reach this agent, and through what." Sections, top to bottom:

Who can chat with this agent?
A single Restricted ↔ Open control:
This is the same cross-channel policy described in Access Control— approving a request admits that email on every channel at once.
Public chat model
Pick the Claude model used for public-facingconversations only — the public link, Slack/Telegram/WhatsApp channels, and paid chat. Your own authenticated chats and scheduled runs are unaffected. The default option ("Use platform default") inherits the platform-wide model; selecting a model overrides it for this agent's public surfaces.
Additional instructions — public & channel chats only
A free-text field (up to 4,000 characters) injected into the agent's system prompt for outside audiences only: public links, Slack/Telegram/WhatsApp, and paid chat. It does not affect your own authenticated chats, scheduled runs, loops, or agent-to-agent calls. Use it to set tone, disclosure rules, or scope limits for strangers without touching the agent's core instructions. Leave empty to disable. (Voice/VoIP has its own prompt — see Voice Chat.)
Channels
Compact status rows for Slack, Telegram, WhatsApp, and Voice calls (when VoIP is enabled platform-wide). Each row shows a connection status dot and a Configure (not connected) or Manage(connected) button that opens the channel's full configuration in a dialog. Per-channel setup guides:
Each channel dialog also carries that channel's voice-replies allow flag — replies are text by default and the agent opts individual replies into voice per message. See Voice Replies.
Portal clients
A list of the people you've shared this agent with, as Workspace (client portal) sign-ins: each row shows when they were last seen, whether they are blocked, and when their sessions were last ended. Refresh reloads it.
Both actions are recorded in the audit log, and an agent's own API key cannot perform them.
Client roster — who's reaching this agent
A table of external channel users who have messaged the agent, aggregated across Telegram and WhatsApp (more channels to follow): client name, channel, verified email, message count, last-active time, and access, ordered by most recent. The roster is database-sourced, so it renders even when the agent container is stopped.
Each row has its own controls:
Each action affects this agent only, is available to the agent's owner (and admins), and is recorded in the audit log.
Distribution
One collapsible panel for distributing the agent's output rather than granting access:
File sharing — signed download URLs for files the agent publishes — is under Settings › Storage, because it governs what leaves the agent's disk; see Agent Files.
For Agents
| Endpoint | Method | Description |
|---|---|---|
| /api/agents/{name}/share | POST | Share agent with an email address |
| /api/agents/{name}/share/{email} | DELETE | Remove a share |
| /api/agents/{name}/shares | GET | List all shares for an agent; each carries proactive_consent (not_asked, declined or consented) |
| /api/agents/{name}/access | GET | Roster of people the agent is shared with (active + pending) for Settings › People, with each row's proactive_consent |
| /api/agents/{name}/shares/proactive | GET / PUT | Per-recipient proactive-DM permission; PUT body {email, allow_proactive} (owner/admin) |
| /api/agents/{name}/clients | GET | External client roster with each client's client_id and access state (owner-only) |
| /api/agents/{name}/clients/block | POST | Block one channel client on this agent; body {channel, client_id, reason?} (owner/admin, people only) |
| /api/agents/{name}/clients/unblock | POST | Lift that block; body {channel, client_id} (owner/admin, people only) |
| /api/agents/{name}/clients/revoke | POST | Remove an approved client's access to this agent; body {channel, client_id} (owner/admin, people only) |
| /api/enterprise/client-portal/agents/{name}/clients | GET | Portal clients with last-seen, block and session state (owner/admin; the prefix is historical) |
| /api/enterprise/client-portal/agents/{name}/clients/{email}/logout | POST | End the client's live Workspace sessions (owner/admin, people only) |
| /api/enterprise/client-portal/agents/{name}/clients/{email}/block | POST / DELETE | Block (optional {reason}) or unblock the client platform-wide (admin, people only) |
| /api/agents/{name}/public-prompt | GET / PUT | Public/channel-only custom instructions (owner-only, ≤4000 chars; empty clears) |
| /api/agents/{name}/public-channel-model | GET / PUT | Public-channel model override (owner-only; null clears to platform default) |