Update and uninstall

Both actions start from the Package's page in Studio → Packages, and both are only available for an installation that finished (Installed or Needs finishing).

Updating a Package

You need the package.update permission. Choose Update, then upload the new version's .pkg.

Before anything changes, you see a plan, compared against what was actually installed:

• what the new version modifies, adds and removes, object by object,
• conflicts: objects you edited after installing that the new version also changes. For each one choose Keep mine (leave it exactly as it is) or Take theirs (replace it with the new version's). Nothing is overwritten without an answer,
• objects the new version drops but something still uses. They stay, as your own resources,
• a change to what the Package declares about data, shown separately and prominently. You must confirm you've read it before updating.

Your model choices carry over

The update keeps the answers you gave when you installed: each model, credential, Knowledge Base, voice provider or phone line stays bound to what you chose, as long as the new version still has that Slot and it is still the same kind of Slot. The plan shows each model role with your current choice already selected. Pick another one there if you want to change it.

It asks again only when it can't reuse an answer:

• A new model role. The new version needs a model the installed one didn't have. Choose one before you can apply the update.
• A Slot that changed kind. If the author turned a Slot into a model role, choose a model for it.
• An installation from before answers were kept. Older installations don't have your choices on record, so you choose each model once more. The update records them for next time.

A new Slot that isn't a model (a credential, Knowledge Base, voice provider or phone line) doesn't block the update. It's listed as Left for later, and you bind it on the Package's page afterwards. If an update can't bind a Slot, the message names the Slot and says what to do.

Choose Update this Package to apply it. The update is recorded as a new installation; the previous one is marked Superseded, and its objects carry on under the new record.

Uninstalling a Package

You need the package.uninstall permission. Choose Uninstall.

Uninstalling stops the Package running: its entry point and its triggers (schedules, webhooks, phone routing) are removed. Everything else it created is left alone unless you say otherwise, because it's an ordinary resource of yours now.

The confirmation lists what the Package originally installed. Tick only what you want deleted. Anything still used by something else, whether one of your own Teams or another object from the same Package, can't be removed and says why. Then choose Uninstall, keep everything else (or the equivalent, if you ticked items).

Two things appear on the confirmation and can't be ticked:

• Already yours — resources the Package used rather than created. They predate the install and are untouched.
• Kept by the author's declaration — Data Tables the Package author declared should survive uninstall, because what's in them is your data rather than the Package's structure. They stay as ordinary Data Tables you own; delete one yourself from Studio → Data Tables if you no longer want it. An author can instead declare a table as scratch space the Package owns, which puts it on the tick list like anything else — still only removed if you ask for it, unless the table is the Package's own entry point, which comes down with it. See Data Tables in Packages.

An install that stopped partway isn't uninstalled but rolled back. See Installed Packages.