Audit trail saves date, "new" and "old" values, operator user identity, as well as other information about requester if available (such as database user and server identities).
Data changes in the following data entities may be configured to leave data audit trail:
- User standard fields
- User global custom fields
- User application custom fields
- User application configuration directory keys
- User membership in user groups
- User membership in application roles
- User relation with other users, companies and products
- User additional (multiple) email addresses, street addresses, web addresses and phone numbers
- Application custom fields
- Application configuration directory keys
- User group custom fields
- Application role custom fields
- Company custom fields
- Company relation with users, other companies and products
- Company additional (multiple) email addresses, street addresses, web addresses and phone numbers
- Product custom fields
- Product relation with users, companies and other products
- Relation type custom fields
- External directory provider custom fields
- Data store items
Auditing configuration has a high level of granularity - auditing may be enabled for selected data items. For example, user may have many custom fields, and only those selected will be enabled to leave a data audit trail.
Once auditing is enabled for a particular data item, it takes effect immediately.
Arnica UnifiedLogon includes several built-in audit management reports as well as exposes audit data via database APIs (views), which may be used to create reports with custom presentation using Arnica WebReport or other reporting tools.