Ideal-state templates
Workspace templates that customers start their ideal state from, including the built-in Standard, Small office and Regulated templates.
Updated
A template is a starting point for a customer's ideal state: a set of controls, each required or left out, with thresholds. Owners and admins manage templates in Settings → Ideal-state templates.
Built-in templates
| Template | What it means |
|---|---|
| Standard | Every control required. Update windows come from your endpoint policy. The default until you change it. |
| Small office | No disk encryption, application control or on-premises Active Directory. App-based MFA is enough for administrators. |
| Regulated | Security updates within 7 days, critically late after 21, devices offline after 3 days, phishing-resistant MFA for administrators, DMARC at reject. |
Built-in templates can be duplicated but not edited.
Create your own
- Settings → Ideal-state templates → New template, or Duplicate an existing one.
- Give it a name and a description your team will understand ("Dental practices", "Manufacturing with OT network").
- For each control choose Required or Left out, and set thresholds. A reason is optional in a template; it's required when you leave a control out for a single customer.
- Save.
A workspace can have up to 50 templates.
The default template
Make the default sets the template customers follow when they haven't picked one. New customers start on it.
Changing and deleting templates
- Changes take effect at once. Every customer on the template is re-measured: scores, action plans, compliance and reports.
- Customer overrides survive. A control a customer overrode keeps the customer's setting.
- Deleting a template moves its customers to the workspace default. If you delete the default, Standard becomes the default again.
Every change is audited.