Sharing an agent
Giving an agent to a colleague, publishing it to your organisation, and the two warnings worth reading.
Three levels, in increasing order of reach.
1. Share with named people
Manage beside Sharing in the builder, or the share icon on the agent card. This is the ordinary sharing dialog: named people as Viewer or Editor, or the whole organisation.
Viewer can use the agent. Editor can rewrite its instructions and change its tools.
If your agent uses collections the recipients cannot see, the agent will not work for them: it will search documents they have no access to and find nothing, silently.
Asteria notices and offers to share the collections too. Take the offer.
2. Publish to the marketplace
Publish to marketplace in the builder puts the agent in your organisation's library, where any member can find it under Browse and add it to their own list.
Two things to understand before you do:
It runs under their identity, not yours. When a colleague uses your published agent, it acts with their permissions and their connected accounts. It cannot reach anything they could not reach themselves.
They pay for it. The cost of running the agent is billed to whoever invokes it, not to you.
What can block publishing
Personal MCP tools. If your agent uses a tool from a connection that is yours personally, publishing is blocked: nobody else can use it. Remove the tool, or ask your administrator to set up the equivalent as an organisation-wide connection.
What you will be warned about
Two warnings you must acknowledge, and both describe failures your colleagues would otherwise hit at runtime:
A sub-agent not everyone can use. Members invoking your agent get an error when it tries to delegate.
A pinned collection not everyone can see. Worse, because it fails quietly: searches return nothing at all, and the agent answers from general knowledge as though the collection were empty. Nobody gets an error. They just get a worse answer and no reason why.
If you see the second warning, fix the collection's sharing before publishing rather than acknowledging it.
You get a preview of the marketplace card before confirming.
3. Duplication
By default, someone who finds your agent can Duplicate it: they get their own editable copy, and from then on the two are unrelated. Yours does not inherit their changes and theirs does not inherit yours.
You can turn duplication off in the sharing dialog if you want one canonical version everybody uses.
When somebody duplicates an agent that points at resources they cannot access, those are skipped and they are told how many.
Unpublishing
Unpublish removes the agent from the marketplace and revokes every member's library entry. Anyone using it loses it.
Copies people made by duplicating are theirs and are unaffected, which is the practical argument for turning duplication off on anything you may need to withdraw.
Reporting
Any member can Report a published agent to your administrators, with a reason. Administrators see the queue and either unpublish the agent or dismiss the report.
Use it for an agent that gives wrong or inappropriate answers, not for one you merely dislike.
Keeping a shared agent alive
The Usage section shows direct uses, unique users, when it was last invoked, and how many people have forked it.
Published agents rot. The style guide changes, the product is renamed, the tone shifts. If usage is climbing, the agent is important and worth maintaining. If it flatlined months ago, unpublish it rather than leaving a stale one for a new joiner to find and trust.
If Publish to marketplace is greyed out, your administrator has turned the agents marketplace off for your organisation. Named sharing still works.