/msdyn_blobfile/$value)
Revised 03/24/2026
- System Customizer Security Role to enable auditing for a table
- Access to Power Platform Admin Center to change environment settings related to log retention
List Prerequisites Here:
- Prerequisite 1(Linked to Knowledge Article?)
- Prerequisite 2
This Knowledge Article provides an overview of table‑level auditing, identifies which tables have auditing enabled by default in akoyaGO, and outlines best‑practice recommendations for setting audit log retention periods to balance needs with storage management.
When auditing is enabled for a table (aka entity), each record within that table includes an Audit History that tracks changes over time. The audit history shows who made each change, the date and time of the change, and the previous and updated values for audited fields. This allows users to review a complete change log for a specific record without querying system‑wide audit logs.
Below is an example of a Request record's Audit History. You can access Audit History by clicking Related > Audit History:
Auditing is not retroactive, meaning it does not capture changes that occurred before auditing was enabled on the table. Only changes that occur from the point auditing is enabled and forward will be recorded in the Audit History. Earlier updates/historical changes made prior to auditing being enabled for a table will not appear in the Audit History for existing records.
The following is a list of akoyaGO tables that have audit history (auditing) enabled by default.
Entity | Audit Status |
Account | Enabled |
Account Subcategory | Enabled |
Accounting Settings | Enabled |
Assets | Enabled |
Committee | Enabled |
Committee Member | Enabled |
Concept | Enabled |
Config Flag | Enabled |
Connection | Enabled |
Constituent | Enabled |
Contact | Enabled |
Department | Enabled |
Donor Opportunity | Enabled |
Donors & Prospects | Enabled |
DT Accounts | Enabled |
Event | Enabled |
Event Attendee | Enabled |
Event Fee | Enabled |
Field | Enabled |
Field Mapping | Enabled |
Fiscal Year | Enabled |
Foundation Matching Gift | Enabled |
Function | Enabled |
Fund | Enabled |
Fund Fee Formula | Enabled |
Funding Opportunities | Enabled |
Gift | Enabled |
Gift Fee | Enabled |
Gift Payment | Enabled |
GOapply Logs | Enabled |
GOapply Opportunity | Enabled |
GOapply Status Tracking | Enabled |
GOapply User | Enabled |
GOdonate Donation | Enabled |
GOdonate Settings | Enabled |
GOdonate Transaction | Enabled |
GOfund Settings | Enabled |
Goverify | Enabled |
Impact Investment | Enabled |
Impact Payment | Enabled |
Interest | Enabled |
Interfund Grants | Enabled |
Outcome | Enabled |
Page | Enabled |
Payment or Requirement | Enabled |
Phase | Enabled |
Program | Enabled |
Program Budget | Enabled |
Project Area | Enabled |
Proposal | Enabled |
Request | Enabled |
Requested Scholarship | Enabled |
Scheduled Distribution | Enabled |
Scholarship | Enabled |
Security Role | Enabled |
User | Enabled |
For any tables with auditing enabled, be intentional about what you audit and the retention period you choose for audit logs. Auditing captures point‑in‑time activity and can quickly consume audit log storage. Auditing is not data, and enabling it broadly (especially with long retention periods) can significantly increase audit log size, potentially requiring the purchase of additional capacity.
More information, including how to set a retention period for how long audit logs are kept in an environment, can be found here: Manage Dataverse Auditing
