Skip to main content
Agents you create can be shared with other members of the workspace. Configure sharing from the Sharing chip on the agent detail page.

​
Sharing scope

The sharing dialog itself offers the first three scopes only. Org-wide sharing has its own action — see “Share with the whole organization” below — and while it is in effect the dialog’s scope options can no longer be saved.

​
Permissions for people you share with

Along with the scope, choose what the people you share with can do.

​
Share with the whole organization

Sharing an agent beyond its own workspace is a separate action, on the agent detail header next to the sharing chip.
  • Press “Share with organization” and confirm. The dialog explains: “Everyone in your organization will be able to view and use this asset. You can stop sharing at any time.”
  • The header then carries a “Shared” chip, and the agent appears in the agent list of every workspace in the organization
  • “Stop sharing with organization” reverses it — members outside this workspace lose access and the agent returns to the visibility it had before
  • The action appears only in the workspace where the agent was created, only for members with “Can edit” rights, and not while the agent is archived
  • While the agent is shared org-wide, the sharing dialog cannot be saved. It shows a note pointing you back to “Share with organization” or to Organization settings
Organization owners and admins see everything shared this way under “Shared assets” in Organization settings, where they can stop a share (the reason is recorded) or share it again.
Once you edit an agent that is shared org-wide, the header adds “Shared version differs from your latest edits.” Everyone keeps chatting with the current agent — the note is a record-keeping marker, which an administrator clears with “Update shared version” under Shared assets.

​
Proposing sharing changes from chat

While chatting with an agent, you can also ask it to change its own sharing — “share this agent with everyone in the workspace.” The AI shows the change (current scope → new scope) on the “Settings change proposed” card, and nothing changes until you press “Apply changes.” Unlike other settings, an approved sharing change takes effect immediately.
  • Sharing changes — from chat or on-screen — can be applied only by the agent’s creator or a workspace owner
  • The “Specific people” scope cannot be set from chat; choose the members on the sharing screen

​
What “Use only” members see

  • The agent carries a “View only” badge in the agents list
  • The configuration panel stays fully browsable, but read-only: a bar reads “Shared with you for use — this configuration is view-only.” and section actions show “View” instead of “Manage / Edit”
  • Jinba Flow connections show which workspaces are connected, but the individual flow list is visible only to members of the workspace that owns the connection

​
Things to keep in mind

  • Members you share with can use the skills, connectors, and knowledge attached to the agent — through that agent. They never see the connector credentials themselves
  • Agent memory (what the AI learns from conversations) is shared by everyone who uses the agent. See Agent memory for details
  • An agent shared with the whole organization always reads its knowledge in the workspace it lives in. Whichever workspace you chat from, both the knowledge you mention in the composer and the material the AI looks up itself come from the agent’s own attached knowledge — never from your workspace’s catalog
  • If you stop sharing, those members can no longer open their chats with that agent
  • Workspace members who are not members of the organization (guests invited from outside it) do not see agents shared with “Everyone in the organization”
  • Sharing settings cannot be changed while the agent is archived — unarchive it first. The current scope stays visible as read-only