Blueprint Packs
A blueprint pack is a large, curated change set that turns a bare tenant into a working configuration — datastores, forms, views, permissions, workflows and the rest — for a recognisable way of working.
Where to find it
Architect Panel → Configuration:
- Blueprint Packs — available packs, and what has been installed
Architect Panel → Data:
- AI Builder — the alternative when nothing fits
- Sample Data — filling the result so it can be judged
What a pack is, and is not
Packs are human-authored and curated, not generated. Somebody who understood the domain decided what the datastores should be, how they relate, what the workflow is and who should see what.
That is the difference between a pack and starting from a description. A pack embodies decisions somebody has already got right; the AI Builder helps you make those decisions yourself.
Compile, lint, install, upgrade
A pack is compiled and linted before it installs, so a pack that would conflict with what is already there is caught rather than half-applied. Packs can also be upgraded, so improvements to a pack can reach a tenant that installed an earlier version.
When to use one
- A new tenant doing something recognisable — a pack gets you to a working system in an afternoon.
- A standard offering you deliver repeatedly, where every customer should start from the same tested base.
Where what you are building is genuinely unusual, a pack is the wrong starting point — you will spend longer removing what does not fit than you would have spent building it.
Install into an empty tenant
Packs are designed to configure a bare tenant. Installing into a tenant that already has a working configuration is where conflicts arise. If you must, install into a fresh tenant first and look at what it creates before deciding.
Adjust after installing
A pack is a starting point, not a finished system. Expect to rename things to your language, add the two fields your organisation needs, and adjust permissions to your structure. Everything a pack creates is ordinary configuration you can edit.
Worked example
A new customer needs complaints handling. A pack installs the case datastore, stages, obligations for the statutory clock, correspondence capture and a reporting dashboard. Two days of adjustment — their terminology, their escalation route, their published response targets — produces a system that would have taken weeks from nothing.
Recommendations
- Install into a fresh tenant and review before committing.
- Generate sample data straight after installing so you can judge it properly.
- Rename to your language early, before people learn the pack's terms.
- Note which pack and version you installed — it matters when upgrading.