Distribution and installs

Distribution levels

A Kit’s distribution says who may install it.

Distribution	Who can install	Available
`private`	Only the owner workspace	Now
`unlisted`	Any workspace whose admin has the install link	Now
`directory`	Any workspace, found in the Kit directory after a review	Not yet (Phase 4)

A Kit moves private to unlisted when you publish a version whose manifest asks for unlisted and every endpoint host is on a verified domain. A Kit never returns from unlisted to private. To stop new installs, revoke the install link instead.

Directory listing and its review are planned for Phase 4 and are not available yet.

Install links

An unlisted Kit is installed through an install link (kil_…).

Create it on the Kit’s page in the developer portal. It is shown once.
Creating a new link revokes the old one.
The link opens the consent screen in the web app at /app/kits/install?link=kil_….

Share the link only with people who should be able to install the Kit. Any member of a workspace can open it, see the consent screen and file a request; installing still needs an admin.

The consent screen shows what the installer is agreeing to:

the Kit’s identity and developer;
the bot and user scopes it asks for;
its tools, each marked read or write with its data class;
the events it subscribes to and the slash commands it adds;
the model data policy it requests.

All of this is one consent document. Its hash is part of every install, request and upgrade, so what is approved is exactly what was shown.

Install requests

Installs always require admin approval. Members can only request.

A member opens the install link and sends a request for the version they saw.
An admin reviews the request on the same consent screen and approves or rejects it. The member can cancel their own pending request.
Approval repeats the consent hash of the request the admin reviewed. If the manifest changed in between, the hashes no longer match: the consent is stale and the request must be reviewed again.

Admins can also install straight from the link after the consent screen. Installing enables nothing on its own; see Concepts.

Version upgrades

When you publish a new version, each installation is compared with it, field by field.

A version whose consent document is equal or narrower is not wider than the installed one.
Anything wider keeps the installation on the old version: a new bot or user scope, a new tool, a tool that became a write tool or reads more sensitive data, a new event, a new command, a wider external authorization, or a model data request. Admins see Update available, review permissions with the difference, and the installation moves only when an admin approves.
Removed tools revoke the grants that used them.

Plan scope changes accordingly: a new version that asks for more is never applied silently.

What you see as the Kit developer

You see your Kit’s own metadata and its log. You do not see other workspaces’ data. A workspace’s installation reaches your servers only through the endpoints and tokens in your manifest.