Salentica Engage, which is built on top of Microsoft Dynamics 365, comes with several tools to help you manage data. One of these is the auditing feature, which allows you to track changes made to data in Engage. Since, by default, auditing is not turned on, you can start auditing at the organization level to allow auditing for entities and fields. When you start auditing for the first time, auditing is started by default on a lot of entities, including: Relationship, Contact, Lead, Portfolio, Financial Accounts, Product, Task, User, etc. When you turn on auditing, it would make sense to stop auditing the entities that don't make sense for you firm.
In addition to entities and fields, audits also track each time a user logs into your system. If auditing is enabled, CRM automatically creates logs for the changes that are tracked.
You may want to stop auditing for maintenance purposes or when the database space is limited. Stopping auditing at the organization level stops the tracking of changes for the entities or fields for the period for which auditing is stopped at the organization level. When you start organization-level auditing again, the same entities and fields are selected for auditing that were selected when you stopped auditing for the organization.
We recommend, since the audit logs take up space in your database, that you are judicious in what you choose to audit. Only audit the entities and fields that are important to know if and when changes are made. If you need to learn more about your Database Storage, take a look at this article.
To turn enable or disable your Global Audit Settings for you firm, follow these steps:
Settings > Advanced Settings > Settings > Auditing > Global Audit Settings > Start Auditing & Audit user access > OK
Next, you can view the complete list of Entities and their Audit states by clicking on the link at the bottom of the System Settings page.
1. Under Components, choose an Entity, and click on its name to view the General information about the Entity.
2. Scroll to Data Services > Auditing.
3. Check (or Uncheck) the box to choose to Audit the Entity.
4. All fields will begin to be audited. If there are fields you do not want to audit, you will need to open the field and adjust the audit settings.
5. Example: Relationship > Fields > Account Rating > Auditing
You can also start or stop auditing for more than one field at a time.
- Choose the fields you want to adjust Auditing on
- On the Actions toolbar, click Edit
- In the Edit Multiple Fields dialog box, in Auditing, click Enabled or Disabled as needed
- Click Save
Now that you have turned on auditing for these entities and fields, you can view your Audit Summary. If you need instructions on how to do this, please read this article.
Organizations often need to be in compliance with various regulations to ensure availability of customer interaction history, audit logs, access reports, and security incident tracking reports. Organizations may want to track changes in Salentica Engage data for security and analytical purpose.
Auditing is not supported on metadata changes, retrieve operations, export operations, or during authentication.
Supported for auditing
The following lists auditing capabilities:
- Audit of customizable entities
- Audit of custom entities
- Configure entities for audit
- Configure attributes for audit
- Privilege-based audit trail viewing
- Privilege-based audit summary viewing
- Audit log deletion for a partitioned SQL database
- Audit log deletion for a non-partitioned SQL database
- Audit of record create, update, and delete operations
- Audit of relationships (1:N, N:N)
- Audit of audit events
- Audit of user access
- Adherence to regulatory standards
- Auditing APIs for developers
Not supported for auditing
The following lists what cannot be audited:
- Audit of read operations
- Audit of metadata changes
The following bullets identify some key auditing concepts:
You can enable or disable auditing at the organization, entity, and attribute levels. If auditing is not enabled at the organization level, auditing of entities and attributes, even if it is enabled, does not occur. By default, auditing is enabled on all auditable entity attributes, but is disabled at the entity and organization level.
The ability to retrieve and display the audit history is restricted to users who have certain security privileges: View Audit History, and View Audit Summary. There are also privileges specific to partitions: View Audit Partitions, and Delete Audit Partitions. See the specific message request documentation for information about the required privileges for each message.
Audited data changes are stored in records of the audit entity.
Data that can be audited
The following list identifies the data and operations that can be audited:
Create, update, and delete operations on records.
Changes to the shared privileges of a record.
N:N association or disassociation of records.
Changes to security roles.
Audit changes at the entity, attribute, and organization level. For example, enabling audit on an entity.
Deletion of audit logs.
When (date/time) a user accesses Common Data Service data, for how long, and from what client.
Enabling or disabling of field level security by setting the IsSecured attribute cannot be audited.