Sharing an AI agent across teams requires an audience decision, manager approval, and a separate review of the information and actions the workflow may use. In AgentShelf, anyone can submit an agent to an organization or team library. Organization or team managers vet the submission and approve what makes the cut.
Approve the audience deliberately and verify source access as a separate boundary.
Choose the audience before submitting
An approved organization agent is available throughout that organization. An approved team agent is available only to that team's members. Choose based on who should use the job, not simply who helped create it.
For several teams in the same organization, organization availability may fit if the job is suitable for the whole organization. If the work belongs to one team's process, submit it for that team. Resolve audience requirements with relevant managers before describing a team-only agent as shared more broadly. These rules cover sharing inside one organization, not between organizations.
See what an AI agent library is for public versus internal collections. Public discovery, such as browsing the AgentShelf Agent Library, finds candidates; internal approval decides what belongs in your collection.
Submit a reviewable operating brief
Give the manager enough evidence to assess the workflow. A short brief like this one gives the reviewer what they need:
Scroll horizontally to see all columns.
| Item | What the reviewer should learn |
|---|---|
| Job and audience | Who needs the agent and which result it prepares |
| Sources | Which information is approved and who may access it |
| Actions | What the workflow can do and where a person decides |
| Tests | How missing evidence, conflicting records, and out-of-scope requests are handled |
| Ownership | Who handles exceptions and maintains guidance |
| Cost | Who owns the allowance and reviews usage |
A reusable prompt may leave these decisions unresolved. Connect the brief to the permissions review and budget ownership record before routine use.
Follow submission, approval, and availability
- Submit: A contributor proposes the agent for an organization or team library with its intended use and evidence.
- Vet: The relevant manager checks task, audience, boundaries, and operating ownership. Resolve gaps before approval.
- Approve: The manager decides whether the submission is included.
- Verify availability: Check organization-wide availability or restriction to team members, according to the approved scope.
- Review operation: Confirm source access and actions with intended users and revisit after material changes.
Approval for a collection does not grant access to every underlying dataset. Verify source access and tool authority separately. This availability workflow also does not determine who can edit an approved agent; confirm that responsibility through the applicable management process.
Apply the rules to a fictional workflow
Beacon Works has sales and service teams that want a common customer-meeting outline. The job uses an approved general template and produces a draft for a meeting owner. A contributor proposes organization availability because the outline is useful throughout Beacon Works.
The organization manager reviews the job and tests. A sales example contains private deal notes; a service example contains restricted support records. The manager asks the contributor to separate the reusable meeting structure from access to those records. Sharing an agent does not make either team's source material available to the other.
The recommended pilot includes an authorized user from each team and verifies which sources each may supply or read. The manager approves inclusion after the job and boundaries are clear. If the agent serves only the sales process, team availability is the appropriate proposal.
Questions to ask any agent-sharing platform
“Shared” is not one permission. It covers who can use an agent, what information it can reach, who approves it, and who looks after it. Ask each platform how it handles the questions below. The third column shows how AgentShelf answers them today.
Scroll horizontally to see all columns.
| Question | Why it matters | How AgentShelf handles it |
|---|---|---|
| Who can use an approved agent? | The audience should match the job. | Organization approval makes an agent available across the organization. Team approval makes it available to that team only. |
| Who decides what gets added? | Someone has to vouch for each agent. | Anyone can submit. Organization and team managers review submissions and decide what is added. |
| Can each department keep its own data rules? | Shared agents must not widen data access. | Making an agent available does not change who can see the data. Each source keeps its own permissions, so review them for every team. |
| Who can change the agent, and how are changes checked? | A change can break work for every team that uses it. | Name who may edit the agent and how changes are tested as part of the approval, and record it with the agent. |
| Can you see how it is being used? | Owners need to spot problems and costs. | Usage and cost reporting covers spending by model, agent, and workspace where those details are recorded. Decide who on your team reviews it. |
| Can another organization use it? | Sharing outside the company is a separate decision. | Library approval covers your own organization only. |
For a template that touches business-unit data, settle two things separately: who may use the template, and what data each of them may read. Test with a real user from each team before launch.
Sharing an agent is not sharing its results
Sharing an agent decides who may use it. Sharing a finished brief or a set of notes decides who may see that result. One does not imply the other. Before you pass results around, check who the intended recipients are and whether the underlying information is restricted. Workspaces and external agents covers the wider setup.
Keep an owner after approval
Approval is the start of an agent's working life, not the end of the review. Keep a short maintenance record with each approved agent. The maintainer can ask the agent to draft updates from its recent results and the problems users report, then confirm the record.
Shared agent maintenance record (blank)
- Agent and approved audience (organization or team): ___
- Maintainer, and the manager who approved it: ___
- Information it uses and actions it may take: ___
- Last review: date, changes, tests run, open questions: ___
- Where users report a bad result, and who can pause the agent: ___
- What triggers the next review (a source or policy change, a new audience, a failed test, repeated corrections): ___
- Who decides to retire it, and where users go instead: ___
For Beacon's meeting outline, the maintainer reviews each new version of the template, while each team checks its own restricted records. If the agent were asked to send follow-ups instead of drafting them, that would be a new decision about its authority, and it would go back to the manager. Retirement is a decision your team makes and records.
Name who receives problem reports and who brings changes back to the relevant manager. Review audience fit when membership, the task, sources, or actions change. Keep the current operating brief and tests accessible to the people responsible.
Before expanding reuse, verify audience, approval, source access, actions, owner, and spending responsibility. Read change management for ongoing review and AgentShelf's trust boundaries for current product context.