> ## Documentation Index > Fetch the complete documentation index at: https://docs.jinba.io/llms.txt > Use this file to discover all available pages before exploring further. # Share an agent > Configuring sharing scope and permissions 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 One picker answers "who can use this agent." | Scope | Description | | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Just me** | Only the creator can use it (default) | | **Named individuals** | Only the people you pick can use it | | **Entire workspace** | Every member of the workspace can use it | | **Entire organization** | Every member of every workspace in the organization can use it, and the knowledge attached to it becomes readable org-wide. Editing stays with the workspace the agent lives in | ## Permissions for people you share with Along with the scope, choose what the people you share with can do. | Permission | What it allows | | ------------ | ----------------------------------------------------- | | **Use only** | Chat only. No changes to settings | | **Edit too** | Chat, plus changes to settings and attached resources | ## Sharing with the whole organization "**Entire organization**" sits in the same picker as the other scopes, but saving it hands over to a confirmation step rather than saving directly: the dialog explains that everyone in your organization will be able to view and use the asset, and that you can stop sharing at any time. Whether the share also needs an administrator's decision depends on your organization's settings. * Once it is in effect the agent's header carries a "**Shared**" chip, and the agent appears in the agent list of every workspace in the organization * **Stopping the share uses the same picker** — choose another scope and save, and the agent drops back to that scope; members outside this workspace lose access * The **permission** cannot be changed while the agent is shared with the organization. The dialog says as much: stop the share first, then change it * Some organizations allow only owners and admins to share across the organization. Where that applies, the scope is shown but cannot be selected, and the picker explains why — including while a share application of yours is still being reviewed * Org-wide sharing is offered only in the workspace where the agent was created, only to members with edit rights, and not while the agent is archived Organization owners and admins see everything shared this way under "**Shared assets**" in [Organization settings](/en/pages/jinba_app_neo/settings/workspace), where they can stop a share (the reason is recorded) or share it again. Deleting the asset itself closes its share and any pending application automatically, recorded as "**Stopped — the asset was deleted**." 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** * Chat can only move the agent between "**Just me**" and "**Entire workspace**." "Named individuals" and "Entire organization" — including stopping an organization share — stay on the sharing screen, so an organization share always goes through its own flow and whatever review it requires ## 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](/en/pages/jinba_app_neo/agents/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 — and a conversation that is already open cannot be continued either * Workspace members who are not members of the organization (guests invited from outside it) do not see agents shared with "Entire organization" * Sharing settings cannot be changed while the agent is archived — unarchive it first. The current scope stays visible as read-only