Based on our research, even when no changes have been made to a user’s security role or system configuration, there are several common reasons why access to Audit History might be lost:
Entity-Level Read Access
Users must have Read permission on the specific entity to view its audit history. Without this, audit logs won’t be visible, even if auditing is enabled.
Field Security Profiles
If audited fields are protected by Field Security, users need to belong to a Field Security Profile that grants them read access to those fields. Otherwise, audit entries for those fields will be hidden.
Audit Settings on Entities and Fields
Confirm that auditing remains enabled on both the entity and its relevant fields. These settings can sometimes be unintentionally disabled during solution imports or updates.
Ribbon or Form-Level Customizations
The Audit History button’s visibility might be controlled by JavaScript or ribbon rules tied to user roles. Recent UI changes could inadvertently restrict access.
Browser Cache or Client-Side Issues
Client-side caching problems can prevent the audit pane from rendering correctly. Clearing the browser cache or testing in incognito/private mode often resolves this.
Audit Entity Permissions
Access to the Audit Summary View requires Read permissions on the Audit entity itself (found under Core Records in the security role). This permission is sometimes overlooked when cloning or customizing roles.
Audit Log Retention and Pruning
Missing audit logs for older records may result from retention policies or partitioning that archive or delete old audit data.
Security Diagnostics
Utilize the Security Diagnostics tool (available via browser developer tools or XrmToolBox) to verify which roles and permissions the system recognizes for the user. This helps pinpoint permission-related issues.
Hope this helps!
Thanks!
Inogic
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
13
Share
Report
All responses (
Answers (
