Templates let you migrate configuration safely between your Applaud tenants. Instead of recreating settings manually, you can package your configuration as a template in one tenant and then install it in another.
A typical setup includes three tenants:
- Development (Dev) – where you build and test the configuration.
- User Acceptance Testing (UAT) – where business users validate the configuration in a safe, non-production environment.
- Production (Prod) – your live tenant, used by employees.
Using templates ensures that you maintain these environments' consistency and reduces the risk of errors when changes go live.
Why use templates?
Templates are the recommended way to:
- Configure and test new functionality in a Dev tenant without affecting live users.
- Package configuration and migrate it into UAT for user testing and sign-off.
- Move approved configuration into Prod once testing is complete.
- Maintain consistency across all your tenants.
How templates work
- A template is a copy of a tenant's configuration.
- Templates can include models, pages, workflows, and roles.
- Templates do not copy data, unless you select the option to include model data.
For example, you might create a template that includes a new onboarding workflow, test it in Dev, and then migrate it into UAT. After business users approve it, you can install the same template in Prod.
What's included in a template
A template is a package of configuration that you can export from one tenant and install in another. When you create a template, you choose the elements to include, and Applaud automatically picks up any dependencies.
Templates can include:
- Pages – layouts, content blocks, and navigation.
- Models – structures that store your data.
- Workflows – automation rules and actions.
- Roles and permissions – who can access what.
- Other configuration – such as notifications and analytics.
Model data
By default, templates only include the configuration. If you also want to copy model data, you can select this when creating the template. For example, you might consist of reference data like cost centres or policy categories.
Some restrictions apply when including model data:
- You can only select models with fewer than 500 instances.
- Models with foreign keys to other models cannot be included.
- Any data added after the template is created won't be picked up.
This gives you flexibility: you can copy a clean configuration only, or bundle it with sample data if needed for testing.
Best practices
- Keep your Dev tenant clean – use it only for configuration and early testing.
- Use UAT for validation – involve business users to confirm the setup meets requirements.
- Migrate to Prod last – only after UAT sign-off.
- Document changes – keep a record of which templates were installed and when.