Setup guide · from scratch
Configure actions for noncompliance with a grace period
Stops surprise Conditional Access lockouts. Give the mandatory 'Mark device noncompliant' action a grace period and add a 'send email to end user' remediation notice before the block bites.
Step 1. Go to Devices > Compliance and sign in as the Example Company admin.
Screenshot: Compliance policies list (captured during a live customer build — coming to this page)
Step 2. Open the policy (or Create policy > pick platform > Create) and set your rules on the Compliance settings step.
Screenshot: Compliance settings step (captured during a live customer build — coming to this page)
Step 3. On 'Actions for noncompliance' change the mandatory 'Mark device noncompliant' Schedule from 0 to a grace value (e.g. 3 days).
Screenshot: Day-count changed from 0 to the grace value (captured during a live customer build — coming to this page)
Step 4. Click '+ Add' > 'Send email to end user'; Select a message template > Create a remediation message; set its Schedule to 1 day.
Screenshot: Email notification message-template editor (captured during a live customer build — coming to this page)
Step 5. (Optional) Add 'Remotely lock the noncompliant device' with its own schedule.
Screenshot: Remote lock action row (captured during a live customer build — coming to this page)
Step 6. On Assignments add the correct DEVICE group (or user group — never both for the same setting); Review + Create.
Screenshot: Assignments step (captured during a live customer build — coming to this page)
Step 7. Separately check Devices > Compliance > Compliance policy settings > 'Compliance status validity period' (default 30 days) so an un-checked-in device isn't auto-flagged.
Screenshot: Compliance policy settings showing the validity period (captured during a live customer build — coming to this page)
See it on a real device.
Decolla is in private build — early-access members see a build defined, deployed and rolled back first.
Get early access