TalentDeltaShare an agent template with your team
Publishing is not the only way to hand a pack over. A private pack reaches the people you name, and it stays out of the catalogue for as long as you want it to.
The two ways to hand a pack over
| What changes | Published | Shared |
|---|---|---|
| Who can read it | Anyone | The accounts you name |
| Where it appears | The directory and search | Studio, for those accounts |
| What it needs | An approved version | The handles, at upload or after |
Both are the same pack from the same upload. The difference is who holds an access row: a published pack is public, and a shared one is private with an audience.
That is the private-and-public distinction GitHub draws on a repository, with access here held as a list of handles you name yourself (setting repository visibility).
- Share it while the pack is still changing, and publish when it has stopped.
- Share it with the two people who will run it, rather than everyone who might.
- Share client work that should not appear in a public catalogue at all.
Four people on one finance team running the same invoice reader: share it with the three colleagues who will run it, keep it out of the catalogue while the flag format is still moving, and publish it the week the format stops changing.
What your colleague sees
A pack shared with somebody appears under Studio when they sign in, listed with its uploader and everyone else who can see it. It carries a badge for its state: Awaiting review until a version is approved, then Approved, not visible yet.
From there they can read it, download it, and keep it as the pack changes. Every build keeps its own change note, so a colleague can see what moved since they last pulled a copy.
Keeping it out of the catalogue
Nothing about sharing makes a pack public. The directory takes a published pack, and publishing is a press the owner makes on the pack's own row in Studio, so a pack handed to five colleagues stays out of the catalogue until somebody decides otherwise.
A colleague's access is read-only in the ways that matter. They can read the pack, download it and follow its versions. They cannot rewrite the audience, and they cannot publish it.
That button is offered once a version is approved. Sharing before approval works perfectly well, and the review decision arrives on the version rather than on the audience.
Where to go next
Who else can read a template before it publishes, and what they can do with it.
Who can see your agent templatePrivate while it waits, shared with the people you name, visible when you say so.
What review checksWhat a reviewer reads, what gets a template turned down, and when you hear back.