Installing a Package
The install wizard, step by step.
Open Studio → Packages and choose Install a Package. You need a role with the
package.install permission (Owner, Admin or Editor).
Drop the .pkg file onto the page, or click to choose it. The wizard then walks through up to ten
steps. Steps for things the Package doesn't use are skipped: a Package without a phone line
never shows the SIP step.
Before you start
Have ready whatever the Package needs from you: an LLM Configuration (Settings → LLMs), the Secrets its Tools use (Settings → Secrets), your documents, and for a phone Package, an inbound trunk and number (Studio → Telephony). The wizard tells you what's missing, but carrier setup in particular can take days.
1. Review
The file is read without installing anything. You see:
- the signature: who signed it, and whether the file is intact,
- the inventory: every Agent, Team, Workflow, Tool, Skill, Knowledge Base, voice and phone configuration it will create,
- the entry point: what runs when the Package starts,
- the author's declarations: data categories, regions, retention, autonomy and EU AI Act tier. These are the author's own statements, shown as such,
- the triggers: schedules, webhooks, calls, API, or only by hand.
You can rename any object here, e.g. if your Organization already has an Agent by that name. If an object matches one you already have, choose use my existing one or install a fresh copy under a new name.
If the signature check fails, the wizard stops and tells you what to do:
| Message | Meaning |
|---|---|
| Not signed | The author built it but didn't sign it. Ask them to sign it and send it again. |
| Unknown signer | Signed by an Organization whose key you haven't trusted. If you trust them, choose Add signer's public key and select the key file they gave you. |
| Contents don't match | It may have been altered after signing. Delete it and ask for a fresh copy. |
2. LLM
Choose one of your LLM Configurations for each role the Package needs. You'll see which objects each choice affects. This step can't be skipped, because nothing in the Package runs without its models. A Configuration that doesn't meet a role's requirements is listed with the reason.
3. Tools
Connect each Tool to your own account: pick a Secret, or sign in with OAuth. Nothing the author used is carried. Each Tool has a connectivity test. You can skip and connect later.
4. Skills
Each Skill is scanned by your Elizon instance, just now; the author's own checks aren't used. Read any findings and the tools the Skill names, and confirm to install it. Skills from a Package are installed as drafts.
5. Knowledge Base
For each Knowledge Base: choose the embedding model, then upload your files, connect a source (for example a web page and the pages under it), or skip. A skipped Knowledge Base is created empty. It answers nothing until it has content, and the Package's page reminds you.
6. Voice
Choose your speech-to-text and text-to-speech providers and credentials. If the Package records calls, you'll see the message callers hear before recording starts. It's the author's wording, so confirm it's right for where your calls are recorded, or change it.
7. SIP Inbound
Choose one of your inbound trunks and the number the Package answers. Only trunks that are ready are selectable; others are listed with what they still need. A Package never brings a carrier account.
Test inbound: call the number from any phone. The wizard turns green when the call reaches Elizon. Until you activate, the line keeps answering as it does today.
8. Triggers
Confirm or adjust each schedule and its time zone (an IANA name such as Europe/Sofia; local
time is kept across daylight-saving changes). Webhook addresses and tokens are generated at
Activate and shown then. API triggers use the Elizon public API you already have.
9. Validate
The Package's objects are created now, but nothing is live yet. If the Package includes an evaluation suite, it runs against your models, accounts and documents. Read the results, including any failures, and confirm you've read them.
10. Activate
Activating records the install in your audit log and turns the triggers on. The page then shows everything that starts the Package: webhook addresses to copy, schedules with their next run, the phone number it answers.
Finishing later
Steps 3 to 8 (Tools through Triggers) can be skipped with Skip for now. Review, LLM, Validate and Activate can't. The Package then installs as Needs finishing: its entry point works, and everything you skipped stays listed on its page in Studio → Packages until you finish it. Anything that depends on a skipped item, such as a phone trigger without a trunk, isn't live until then.
If something goes wrong
If the install stops partway, nothing is left half-done without a record. Open the Package in Studio → Packages and choose Resume install to continue from where it stopped, or roll it back to remove what it created. See Installed Packages.
Installing from the command line
Developers and CI can install with npx @elizon/cli install. See
install. A command-line install without
--activate shows Activate on its page in Studio → Packages: choose it, upload the same .pkg,
and the wizard walks you to Activate without creating anything again.