By default, each new table definition has the Create Audit checkbox selected. This means that audit data is collected when records are added to, modified in, or deleted from the table. However, users require additional roles to access this audit data, even when they have access to the records themselves. It's important to configure these security objects consistently across all product families so that system administrators can easily provide their users with audit access across their enabled solutions.

Audit access security structure

Each product family requires multiple functional roles that provide different levels of access to the audit data for records in that product family: 

  • A record-audit access role—Allows a user to view the history of individual records in a table.
  • A table-level audit access role—Allows a user to view the history of all records in entire tables. 

Learn more about record-audit and table-audit access in Audit data access levels.

For both record-level and table-level audit access, you should configure an individual permission and duty role for each security group in your product family. Then, you should add these duty roles to a single functional role. 

For example, the Financials product family has both the FINS - Record Audit and FINS - Unrestricted Audit roles, each of which provide different levels of access to audit data in the family. Both roles are comprised of different duty roles that provide the the appropriate level of access to records in the Financials family tables.

Record-level audit

The following table describes the structure of the different security objects needed to provide record-level audit access to tables in a product family:

Security objectDescriptionNaming conventionExample
PermissionProvides record-level audit access to all the tables within a single security group within the product family.<product family abbreviation><security group> - Record AuditdirHolds - Record Audit
Duty RoleProvides record-level audit access to all the tables within a single security group within the product family.
Each audit Duty Role should contain only the record-level audit permission for the security group. 
Each audit Duty Role for the product family should be provided to the associated record-level audit Functional Role.
<product family abbreviation><security group>AuditorRecorddirHoldsAuditorRecord
Functional RoleProvides record-level audit access to an entire family. Every record-audit duty role should be included in this functional role in the Role Hierarchy Definitions application.<capitalized product family abbreviation> - Record AuditDIR - Record Audit

Table-level audit

The security structure for the security objects that provide table-level audit access is similar to that of record-level audit, but each permission has the Unrestricted Access checkbox selected, and the naming conventions are different:

Security objectDescriptionNaming conventionExample
PermissionProvides table-level audit access to all the tables within a single security group within the product family.<product family abbreviation><security group> - Record AuditdirHolds - Unrestricted Audit
Duty RoleProvides table-level audit access to all the tables within a single security group within the product family.
Each audit Duty Role should contain only the table-level audit permission for the security group. 
Each audit Duty Role for the product family should be provided to the associated table-level audit Functional Role.
<product family abbreviation><security group>AuditorRecorddirHoldsAuditorUnrestricted
Functional RoleProvides table-level audit access to an entire family. Every table-audit duty role should be included in this functional role in the Role Hierarchy Definitions application.<capitalized product family abbreviation> - Record AuditDIR - Unrestricted Audit