Marketplace
Reviewed packs, versioned like software.
The marketplace is where a complete campaign is packaged, versioned and installed from. Everything in the catalogue was either published by us or approved before publication: a workspace can submit a template of its own, and it reaches the catalogue only through a review. What it is not is a directory of other companies’ applications. A pack has versions, an install is recorded against the version you took, and the pages below cover everything between that install and the day you take it back out.
In the product
The catalogue, and what you already have.
Before you install
What a pack is allowed to be
A pack is authored somewhere else and materialises into your database as a live journey. That is a trust boundary, and it is enforced by rules rather than by review.
Afterwards
Versions, edits, and getting out
Installing is the easy half. These two pages are the half that decides whether you can live with the thing for a year.
The engine
What a pack turns into
A pack is only a delivery mechanism. What it becomes is an ordinary campaign in your workspace, editable like any other.
Questions
The things people actually ask.
Can I publish my own pack?
You can submit a template for review, and submissions are tracked with a review decision recorded against each one. There are two routes into the catalogue and they behave differently, so it is worth naming both. On the versions route a version exists as a draft before it is published, and publishing it is a deliberate separate act, so a draft is never something a workspace can install by accident. On the submissions route an approval publishes in one step. Either way the package itself is validated against the trust boundary before an install can write anything, so what changes between the two routes is when the catalogue entry appears, not what a pack is allowed to contain.
How do I know a new version exists?
Your installs are recorded with the version you took, and the updates view compares that against what the catalogue publishes now. Nothing is applied from that view: it tells you an update exists, and the preview tells you what it would change.
Is this an app store?
No, and the distinction is worth being blunt about. There are no third-party applications, no directory of other companies’ integrations, no code anybody else wrote running in your workspace, and no revenue share. It is a catalogue of packs – mostly complete campaigns – with versioning and an install ledger. Most were written by us; a submitted one enters the catalogue only after a review, and once it is there any workspace can install it. What a pack can contain is fixed and validated either way, which is what the trust boundary page is about.
What happens to my edits when a pack is updated?
They are attributed to you and kept by default. The update runs a three-way comparison – the version you installed, your campaign now, and the version on offer – and a merge keeps your change wherever you made one. The updates page has the whole lattice.
What can a pack not contain?
Sixteen keys are stripped before anything is written, and two step types are refused outright rather than sanitised. The two most telling entries on the strip list are the ones that would otherwise cost you something: an auto-enrol flag, which an hourly job would honour on the next tick, and the switch that arms per-recipient AI email, which is spend on your account authored by somebody else. A pack cannot turn either on. The trust boundary page names all of it, including why an owner field is removed rather than remapped.
Read a pack before you install it.
Every pack lists what it contains. Nothing about installing one should be a surprise, and that is the part worth checking first.