Installed Packages
See what each Package created, finish what's outstanding, and recover failed installs.
Studio → Packages lists every Package installed in your Organization. You need the
package.view permission, which every built-in role has.
The list
Each row shows the Package's name, namespace, version, status, when it was installed and who signed it.
| Status shown | Meaning |
|---|---|
| Installed | Everything is set up. |
| Needs finishing | Working, with items you chose to finish later. |
| Interrupted | An install that didn't finish (a closed browser, a stopped command). Resume it or roll it back. |
| Install failed | Stopped partway on an error. Resume it or roll it back. |
| Rolled back | A failed install was undone. |
| Uninstalled | Removed. |
| Superseded | Replaced by a newer version through an update. |
A Package's page
Select a Package to see:
- Objects: everything it created, each linking to the resource, plus anything it reused from what you already had (reused objects stay yours even if the Package is rolled back).
- Outstanding: every item still to finish, by name: a Slot that was skipped, a Knowledge Base with no documents, a trigger that isn't live. Each one says what's needed.
- Compliance changes: if a newer version changed what the Package declares about data.
- Actions: Activate, Resume install, Update, Uninstall, depending on its status and your permissions.
Every resource a Package created also shows, on its own page, which Package installed it.
Activating a Package installed from the command line
A Package installed with npx @elizon/cli install (without --activate) is created but not live.
Its page says Installed but not activated yet, and a role that may install sees Activate:
- Choose Activate. The install wizard opens for that installation.
- Upload the same
.pkgthat was installed. A different Package or version is refused. - Walk through the steps. Nothing is created again: your schedule and phone-line answers are used to turn the triggers on. Models, Tool credentials, documents and voice settings keep what was set at install; change those on each object's own page.
- Read and confirm the evaluation results (if the Package has a suite), then Activate.
A Package is activated once. After that, Activate no longer appears.
Finishing outstanding items
- Credentials: choose Bind next to the outstanding Slot and pick the Secret. Elizon writes it into every Tool that uses it.
- Speech providers and phone lines: the outstanding Slot shows the same choices the install wizard offers: a provider and its Secret, or one of your inbound trunks and the number it answers. Choose, then Bind. A phone line bound on an active Package starts answering straight away.
- Knowledge Bases: add documents to the Knowledge Base; the reminder clears once it has content.
- The Package shows Installed once nothing is left. Binding needs the Owner, Admin or Editor role.
- Developers can bind the same Slots from the command line with
packages bind.
Recovering a failed install
A failed or interrupted install keeps a record of every object it created. Choose:
- Resume install, which reopens the wizard and carries on from the object that failed, reusing everything already created, or
- Roll back, which removes everything this install created. If something outside the Package now uses one of those objects, it's kept and listed rather than deleted.
An install started from the command line can be resumed or rolled back here, and vice versa.
Command line
npx @elizon/cli packages ls shows the same list, including every outstanding item, for scripts that
check several Organizations. See packages ls.