Packages

A Package is a ready-made solution: a set of Agents, Teams, Workflows, Tools, Skills, Knowledge Bases and, if needed, a phone line, that installs into your Organization as one unit. Someone builds it once (Elizon, a partner, or your own developers) and sends you a single .pkg file.

What you bring, and what the Package brings

A Package brings how the solution works: the instructions, the steps, the rules. It never brings anything that belongs to you. When you install, you connect:

• your models: one of your LLM Configurations for each role the Package asks for,
• your accounts: credentials from your own Secrets (a calendar, a ledger, a speech provider),
• your documents: for any Knowledge Base,
• your phone line: your own trunk and number, if the Package answers calls,
• where results go: your own Slack channel, email recipients or webhook.

Nothing is shared with the author, and the author's accounts are never used.

Before you install anything, you see everything

The first step of the install wizard reads the file without installing it, and shows you:

• every object it will create ("3 Agents, 1 Team, 1 Workflow, 1 Tool, 1 Knowledge Base…"),
• what the author declares about data: categories, regions, retention, autonomy, EU AI Act risk,
• what starts it: schedules, webhooks, phone calls, the API, or only by hand,
• who signed it, and whether the file is intact.

Leaving at that point leaves no trace in your Organization.

After install, it's yours

Everything a Package creates is an ordinary resource of your Organization. You can open, edit and reuse its Agents and Workflows like anything you built yourself. Studio → Packages keeps track of what each Package created, what's still unconfigured, and what has changed.

Who can do what

Next

• Installing a Package
• Installed Packages
• Update and uninstall
• Building your own? See Developer Resources.