Who can see your agent template

Every pack is created private, and a private pack is readable by the accounts on its access list. Nobody else sees it: not the catalogue, not search, not a signed-out visitor who has the link.

Its audience is the handles you name, up to twenty of them. Handles rather than email addresses, because an audience is a list of accounts. A handle that belongs to no account is refused before the upload is accepted, so a typo is caught at the door.

A list of named accounts rather than a link anybody can pass on is the arrangement least privilege describes: access for the people who need it, and no further (NIST's definition).

Those accounts see the pack under Studio, listed with its uploader and the whole audience. A reader can see at a glance whether a pack is theirs alone or shared with five colleagues.

That list can be rewritten afterwards, and only by the pack's owner. It is the one thing about visibility that changes: handles can be added or removed later, and nobody else can touch the list.

Two facts decide what the world sees, and they are not the same fact. Most of the confusion about an "uploaded" pack is these two being read as one.

• Approval gives the pack a page. Until a reviewer approves a version there is nothing at the template's address to open, and Studio says Awaiting review.
• Visibility puts that page in the directory. Approval on its own leaves the pack out of the catalogue, with Studio reading Approved, not visible yet.

Once a version is approved, the owner's own row in Studio carries Make visible. Press it and the pack joins the directory, and the row leaves that list, because the list is the private packs.