Your assigned roles determine what level of access you have to audit data. Options include:
- Record-level audit access—Users with record-level audit access can use the Audit History for Record action in an application. This opens the Audit History Viewer mini app, where they can view a detailed history of all the changes made to the record.
- Access to audit data relies on using a row action on a record, which means these users must first have access to view the record itself.
- Table-level audit access—Users with table-level audit access can open the Audit History Viewer mini app from the Navigation menu and view a history of all the changes made to all records in a given table.
- Security administrator-level access—Security administrators can use the Audit Log Configuration Utility and Audit Log applications to view the changes made to records across the environment based on defined filter criteria. They can also export these records.
Learn more about the different audit applications in the Audit History Viewer mini app and Audit log topics.
Audit security administration
With a few exceptions, the ability to access audit data for records also requires access to the records themselves. For example, a user with record-level audit access cannot view the audit data associated with a record they do not otherwise have permission to access.
System administrators can learn about providing their users with the necessary roles to access audit data in Audit security administration.
Audit security development
Application developers must create the related security objects required for users to access audit data when they develop new table definitions for their applications. They should follow best practices to ensure the security administration process is consistent. They can learn more in Audit security development.