1. Select a property
Open a Property Identity your organisation is authorised to access.
A practical five-step workflow
How Property Compliance works
Select a governed property, add organisation-defined requirements, record sources and evidence, review dates and status, then act on visible gaps.
What this means in practice
The Compliance view is a focused entry into the existing Atlas module. It reads and changes the same permission-scoped records; it is not a second compliance database.
2. Define requirements
Record the checks, documents or dates your organisation has decided to monitor.
3. Attribute evidence
Keep source and review state with each record. Arrange secure transfer before sharing files.
4. Review status
Track current, due, missing and archived records with version history.
5. Agree action
Make gaps visible to authorised users; the service does not claim that an action has happened until it is recorded.
One account, explicit entitlements
Start FreeStart with the property. Add Compliance when it is provisioned.
The record and history stay shared with Atlas; navigation can remain focused.