Audit trails are one of the most reliable ways to answer a simple question with confidence: what changed, who changed it, and exactly what was different before and after?
If you’ve used audit trails in the system before, you already know they’re invaluable for troubleshooting, compliance, and day-to-day accountability. Now that capability has been expanded to include something many organizations care deeply about:
- Changes to permissions (also known as security profiles)
Below is a clear walkthrough of how audit trails work, how to read them, and what’s new.
How audit trails have worked for years
Under Maintenance, you can access Audit Trails and review changes across key record types (for example, site-related updates).
To run an audit trail:
- Select the area you want to audit (such as changes to sites)
- Choose a date range
- Run the search
How to read an audit trail entry
Each audit trail result is designed to show you both context and precision.
You’ll typically see:
- Date and time the change occurred
- User who made the change
- Record the change was made to (for example, a site, family, or financial transaction)
- Action type (such as update or delete)
- Versioning details (the system keeps prior versions)
- Field-level changes showing the old and new values
That last part is where audit trails shine: you can see exactly what was modified within the record—such as a corrected spelling in a last name, capitalization adjustments, and even updates to key dates (including both Gregorian and Hebrew dates of death when applicable).
Not time-bound: historical changes remain available
A major strength of the audit trail is that it’s not limited to a short retention window. If a record was updated years ago and updated again recently, those changes can still appear—giving you a complete story of how the record evolved over time.
What’s new: audit trail for permission (security profile) changes
The newest expansion adds audit trail visibility into permission updates—in other words, changes to what users can do after they log in.
This means when a security profile is modified (for example, changing multiple permissions from No Access to Read Only, or adjusting a specific permission from Write to Read Only), those changes can now be audited.
To view permission-change auditing:
- Open the Audit Trail on Permissions
- Narrow the range to the timeframe you want to inspect (for example, starting from the current day)
- Review the results to see a list of permission fields that changed and the before/after values

You’ll see each permission adjustment listed clearly—such as repeated transitions from No to Read Only across multiple entries, along with any other permission refinements made during the same period.
Why this matters
Permission changes are among the most sensitive updates in any system because they directly affect access and control. Having an audit trail for these updates supports:
- Security reviews (confirming what access was granted or restricted)
- Compliance and internal governance (proving when and how access changed)
- Operational clarity (reducing confusion when a user reports different access than expected)
Takeaway
Audit trails have long provided detailed, versioned visibility into record changes. Now, that same transparency extends to security profiles and permission updates, giving you a clearer, more accountable view of access control changes across your organization.
See the full video: https://share.shalomcloud.com/7KuGqYb6






