Lifecycle
A tool moves through three steps. Admins control the first and last. Employees take the middle one.
Approve
Section titled “Approve”A builder publishes a tool, or the runner finds one already on a laptop. Nothing reaches the whole organization until an admin approves it. Approval is recorded with who made it and when.
- The organization’s catalog shows only approved tools. A builder’s private tools stay visible to the builder.
- Every new version is a new decision.
- Tools adopted from laptops go through the same review.
Install
Section titled “Install”An employee picks an approved tool in the portal and chooses the device. The runner on that device sets it up and the tool appears in the AI client.
- Installing is a click. There is no extra step in a terminal.
- Tool definitions are verified before they run.
- Installs belong to one device. Sign-ins to connected services belong to the person, so a second laptop does not mean a second sign-in.
- If a tool connects to a third-party service through Scenery’s sign-in, the employee approves it once and never sees or holds the service’s credentials. Some tools use the employee’s own API key instead. See Sign in to connected tools.
See Devices, Accounts and Tool sign-in.
Revoke
Section titled “Revoke”An admin can remove a tool from every device, cut off one device, or cut off a person, all from the portal.
- A device that is online removes the tool right away. A device that is offline finishes the job when it reconnects.
- The portal shows progress, for example how many devices have removed the tool.
- Removal puts the laptop back the way it was. Things the employee had before Scenery stay in place.
See Kill switches and Uninstalling.