Why Need Auditing ?
Microsoft Dynamics CRM 2011 offers auditing features and there are many reasons for an organisation wanting to audit business data.Some are:
- Analyse user actions to improve business processes
- For maintaining history of the business data
- To comply with legal regulations
- To maintain security
Levels of Auditing
There are three levels of Auditing in Microsoft Dynamics CRM 2011
- Organisation
- Entity
- Field
Supported Features
- Organisation Level
- Audit of Areas (Sales, Marketing, Service)
- Audit of audit events
- Audit log deletion
- Entity Level
- Audit of custom and customizable entities
- Audit of create, update and delete events of records
- Audit of changes to the shared privileges of a record
- Audit of relationships (1:N, N:1, N:N) - Associations or disassociations
- Audit of privilege changes (changes to security roles)
- Field Level
- Audit of fields of custom and customizable entities
- Audit of update event of fields
Unsupported Features
- CRM cannot audit/log who reads data and when
- this includes reading data on forms, views, reports and data exports
- CRM cannot audit/log changes to metadata, for example renaming a field
Key Concepts
- Auditing can be enabled at Organisation, entity and field levels. CRM will ONLY start auditing the data when auditing is enabled at the Organisation level (enabling at entity and field level will not start auditing)
- Audit data is stored in a database table, it is not represented as an entity within the Organisation
- Audit data is divided logically into quarterly segments called "Audit Logs", Audit Logs can be individually deleted to free up some space.
Audit Permissions
Only System Administrator and/or System Customizer has rights to enable or disable Auditing at the Organisation level.
Other auditing permissions which can be granted by configuring security roles
- View Audit Partitions
- Delete Audit Partitions
- View Audit History
- View Audit Summary
Refer to Microsoft's documentation for more information.
No comments:
Post a Comment