Build
Installations
How a project gets into a hub, what the install screen shows, and what happens on uninstall.
Installing puts the project's agent into a hub with a managed role holding the granted capabilities. Only people with Manage Hub can install, and they can grant fewer capabilities than requested.
Ways to install
| How | Environment | Notes |
|---|---|---|
| App Market → Add to Hub | Production | Only for public projects (Project Settings → Listing). |
| Install link | Production | Private projects too. GET /applications/:id/install returns what the screen shows. |
OAuth with agent.install | Production | From your website: the person picks the hub on the consent screen. |
| Agents → Install in a test hub | Development / Staging | Into hubs you manage. See Environments. |
| Sandbox hub | Development | One click from Templates & Sandbox. |
After installing
- The agent receives
SERVER_CREATEand starts getting the hub's events; subscriptions receiveinstallation.created. - Global commands appear in the hub immediately. Hub-specific commands can now be published for it.
- The installation is recorded in the hub's audit log and in your project's Installations list.
Uninstalling
A hub manager can remove the app at any time (Hub Settings → Integrations). The agent leaves, its managed role is deleted, hub commands for that hub are removed and you receive installation.removed.
| GET | /servers/:id/integrations | Apps installed in a hub (for hub managers and agents) |