TalentDeltaName your collaborators
A private template is readable by the people you name. This is who they are, what they can do with it, and the two things only you can do.
The handles you name
An audience is a list of handles, up to twenty, given when the pack is created or added by its owner afterwards. Every handle has to belong to an account: the upload is refused outright if one does not, and the same rule holds when the list is rewritten later.
If you know GitHub's version of this, it is the collaborator list on a private repository rather than a public one: named people, invited one at a time, discoverable by nobody (inviting collaborators).
A handle is a public name. Add somebody by the handle they chose, not by the address you know them at, because an address is not a directory entry and will not resolve.
What they can do
They can read the pack, download it, and follow it while it waits for review. Publishing is not theirs to do: Make visible refuses anyone but the pack's owner, which is worth knowing before you promise a colleague that they can put it up.
They see it under Studio, alongside the pack's uploader and the whole audience. The list sits on the row, so nobody has to ask who else is reading.
| What sits on the row | For a pack with three handles |
|---|---|
| The pack | invoice-reader |
| Uploaded by | @ada |
| Audience | @ada, @marco, @priya |
| State | Awaiting review |
| Owner's action | Make visible, once a version is approved |
That row is an illustration of the shape rather than a real one, but the fields are the fields: everyone who can read the pack is named on it, so a collaborator never has to ask who else is reading.
When you hand the pack over, say which two files matter. Most questions from a collaborator are answered by the README's quickstart and the newest version note, and pointing at those two saves a round of messages.
invoice-reader is in your Studio under Awaiting review. Start at the README's Quickstart section, then read the newest version note: the flag file is now flags.csv, not hits.csv.
What only you can do
- Rewrite the audience. The access list is the owner's write, and it is the only way to add somebody to a pack that already exists.
- Publish it. The pack's visibility changes on the owner's press and nowhere else.
Nothing about a private pack is edited in place by anyone. A change to the pack is a new upload, and the audience you named keeps its access to the pack across it.
Where to go next
Hand someone a pack without publishing it to the catalogue.
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.