For example, you could assign roles to a user that allow them to view the history of changes made to entire tables in the Manufacturing product family, view the history of changes made to individual records in the Directory product family, and prevent them from viewing any audit data in the Financials product family.

In general, for a user to access audit data for one or more records, they need to have different roles that allow them access to:

  • View the records.
  • Use either the Audit History Viewer or Audit Log applications.
  • The audit data for the records. There are different audit roles available for each product family.

Roles to access audit applications

The following table describes the roles needed to access the different audit applications:

Functional roleAudit applicationsConsiderations
SYS- Record Audit
or 
SYS - Compliance Officer
Audit History Viewer
Audit History Generation Utility
Users do not need these roles to open the Audit History Viewer application using the Audit History for Record row action, provided they have access to the audit data for that record. 

However, users need one of these roles to access these applications from the menu.
SYS - Security Administrator
Audit Log Configuration Utility
Audit Log
Users with this role cannot use the Audit Log Configuration Utility application to generate a query for audit data they do not have access to. However, if another user generates that data, they can see it in the Audit Log application.

For example, a security administrator without access to financial records could view any financials audit data generated by a different security administrator in the Audit Log application.

Roles to access audit data in a product family

The following table describes the functional roles required to access audit data in a particular product family:

Access levelDescriptionExample functional roleConsiderations
Record-levelAllows access to the audit history of individual records in a given product family using the Audit History for Record action.DIR - Record Audit—Allows access to the audit data for individual records in tables that are in the Directory product family.A user may be able to view restricted fields in the audit data for a record, even if their roles and permissions prevent them from accessing them in the application.
Table-levelAllows access to the audit history of all records in all tables in a given product family.

FINS - Unrestricted Audit—Allows access to the audit data for all tables in the Financials product family.

A user may be able to view audit data for records that they are prevented from accessing due to org unit security.

Example role assignments

For example, you may have a group of users that all have access to records in the Directory product family. The following table describes each user, the different roles they have, and how those roles result in different levels of audit access:

UserAssigned audit rolesDescription of audit access
AustinNoneAustin cannot access audit data.
ShannonDIR - Record AuditShannon has record-level access to audit data in the Directory product family. She can use the Audit History for Record action to see the history of changes made to the record in the Audit History Viewer application.
ToriSYS - Compliance Officer
DIR - Unrestricted Audit
Tori has table-level access to audit data in the Directory product family. She can launch the Audit History Viewer application from the navigation window and see a history of changes made to the records in a Directory table.
They can also use the Audit History for Record action to audit a single record.
DaraSYS - Security Administrator
SYS - Record Audit
DIR - Unrestricted Audit
Dara has:
  • Table-level access to audit data in the Directory product family. They can launch the Audit History Viewer application from the navigation window and see a history of changes made to the records in a Directory table.
  • Access to use the Audit History for Record action to audit a single record.
  • Access to the Audit Log Configuration Utility and Audit Log applications, where they can query, view, and export audit data for records in the Directory product family.
KimberlySYS - Compliance OfficerKimberly can open the Audit History Viewer application from the Navigation menu, but she is not able to view any audit data for records in the Directory family.
DuncanDIR - Unrestricted AuditDuncan technically has access audit data for records in the Directory family, but he cannot use the Audit History Viewer or Audit Log applications to view the audit data.
A system administrator should evaluate the audit roles assigned to Duncan.

Learn more in Audit security administration best practices.

Audit log

System administrators use the Audit Log Configuration Utility and Audit Log applications to examine the changes made to records across their environment from a central location.

By default, audit data is stored alongside the records they capture information about in secured tables. Users with table-level audit access can view all the changes made to records in a single table, but the only way to view audit data from across your environment, and the only way to export audit data, is to add it to the audit log.

Use the following applications to collect and view audit data in a central location and determine if business protocols are being followed:

  • Audit Log Configuration Utility application—Define criteria for the audit data you need to examine, and select the Generate Audit action to populate the SystemLevelAudit table with the audit data matching that criteria. Your audit can be specific to certain users, tables, timeframes, and more.
  • Audit Log application—View the audit data that's been added to the SystemLevelAudit table. This application stores all results of all generated Audit Log Configuration Utility records. To view the results of a single configuration, filter the records by its Label, which is a unique identifier of an audit log configuration record.

For example, you could configure and generate a query of all the changes made to Directory records by Eli Cash last March. Then in the Audit Log application, filter for that query to examine Eli's activity.

Export audit data

The only way to export audit data is from the Audit Log application, which is built over the SystemLevelAudit table. There are multiple ways to export audit data:

  • Directly from the Audit Log application with the Export CSV form action. The CSV file contains the records exactly as they display in the application, including filters, sorts, and column order. 
  • Using a data export. The export can be downloaded or sent directly to an external system. Learn more in Data export process.

Audit Log Configuration Utility application

System administrators use the Audit Log Configuration Utility application to specify a criteria of audit data and add that data to the Audit Log application, where it can be viewed and exported.

You can filter audit records by date, time, users, and tables to access a history of the changes made to data across the environment. Each record in the Audit Log Configuration Utility application represents one unique filter criteria of audit records. 

The Audit Log application stores the results of all those criteria in a single table. Enter a unique name for your audit log configuration record in the Label field to access the results of a specific configuration in the Audit Log application.

To create an audit log configuration record, specify the parameters of the data you need to audit. For example, you could configure a query to find all the changes to records made in the Directory table by Blake Jones in March of 2021, or to find all the changes made by all users to all system tables yesterday.

After you save your audit log configuration record, use the Generate Audit button to populate the Audit Log application with the audit records that match the criteria of your configuration.

Audit Log application

System administrators use the Audit Log application to view and export audit data.

Each record in the Audit Log application represents an instance when a user inserted, updated, or deleted a record. You can see the table where the change was made, when the change was made, the user who made the change, and exactly what the change was. Each change is automatically assigned a unique Audit ID. In the detail form, you can see additional information about workflow and a complete view of the old record, the new record, and the difference between them.

Learn more in Audit log.

Audit History Viewer mini app

Use the Audit History Viewer application to view a history of changes made to different records.

Each record in the Audit History Viewer application represents a single modification to a record. You can see what the changes are, who made those changes, and when the changes were made. Use the Edit button to examine the modification in more detail.

For example, if you notice that a customer record was deactivated, you could audit the customer record to determine how long they have been deactivated, and the user who deactivated them. 

Learn more about audit data in Audit data access levels.

Depending on your level of audit access, you may be able to view a history of changes made to a single record, or a history of changes made to all records in a given table:

  • Record-level audit access—Users with record-level audit access can open the Audit History Viewer application using the Audit History for Record action on a record in an application. This allows them to view all the changes made to the record.
  • Table-level audit access—Users with table-level audit access can open the Audit History Viewer application from the Navigation menu and specify a specific table to audit. Unlike users with record-level audit access only, these users are able to view all changes made to all records in the specified table.

System administrators can provide their users with these different levels of audit access. They can learn more in Audit security administration.

Audit History Generation Utility application

System administrators use the Audit History Generation Utility application to generate values in the Change List field on the audit data for different tables. This application only needs to be used if filtering on the Change List field is required while auditing table records.

To generate the Change List values, select the Create button and enter a list of tables that require filtering on the Change List field. Then, select the Generate Audit History form action. After the job is complete, you can use the Audit History Viewer application to view a history of changes made to records in those tables, and filter the audit data using the Change List field.

Audit security administration best practices

These best practices ensure the roles needed to access different levels of audit data are administered consistently across the platform.

In general, you should provide:

  • Record-audit access to business users, for the business domains they operate in.
  • Table-level audit access to system administrators, for the business domains they operate in.
  • Security administrator-level access to security administrators who can be trusted with potentially sensitive data.

Learn more in: