Sign in as an administrator.
- Overview of Adobe Acrobat Analyzer
- System Requirements
- Product Constraints
- Transaction consumption for Adobe Acrobat Analyzer
- Release Notes
- Technical notes and release schedule
- Admin and configuration
- Documents and Collections
- Attributes
- Integrations
- SharePoint setup
- Support
Track who did what, when, and to which documents, attributes, or collections—all in one searchable, exportable audit log.
The Audit Report provides a complete record of activity across your Adobe Acrobat Analyzer organization. Admins can use it to investigate issues, support compliance reviews, and maintain visibility into document, collection, attribute, automation, and permission changes.
Only admins with the appropriate permission can access the full audit history.
Note
Admins can only manage permissions for their users’ collections and files. If a user's collections or files must be deleted—for example, if they are deactivated or no longer have access to Acrobat Analyzer—the admin must submit a support request, and Adobe will complete the deletion on their behalf.
What the Audit Report captures
The audit report records both user-level and admin-level actions. Each entry includes the timestamp, user, role, action taken, the affected object, status (when applicable), and metadata.
User-level events
These events record actions taken by standard users. Examples include:
- Document management
- Upload documents.
- Delete documents.
- Add documents to collections.
- Remove documents from collections.
- Download documents.
- Export to CSV.
- Collection management
- Create or delete a collection.
- Share or unshare a collection.
- Unlink a linked SharePoint collection.
- Integration management
- Add, configure, refresh, or remove a SharePoint integration.
- Attribute management
- Create, edit, or delete a custom attribute.
- Upload or download an attribute list.
- Automation management
- Create, edit, or delete an automation.
Admin-level events
Admins see all user-level events, plus:
- User and permission change
- Grant or revoke user permissions (collection sharing, attribute creation, asset sharing).
- Settings changes
- Export Audit Logs.
- Other admin-only actions as the feature expands.
System events
Some actions trigger additional system-generated events. For example:
- Document ingestion success/failure.
- Hard deletion following a user-initiated soft delete.
- Automated extraction.
How long is audit data retained
Audit history is stored for 12 months by default. Your Adobe account team can configure a different retention policy if necessary.
Note
How audit logs behave when PII is deleted
If a user is removed for GDPR or compliance reasons:
- Email addresses and other PII are anonymized in past logs.
- A placeholder (such as “[deleted user]”) replaces identifying fields.
- The log still preserves the fact that an action occurred.
Generate an Audit Report
Admins can export up to 10,000 events at a time in 90-day intervals.
-
-
Navigate to the Settings tab.
-
Select the Audit logs tab.
-
Select the Audit Report link.
-
User filters to refine the report:
- Select 1 - 10 users (admin-only filter; supports search and multi-select).
- Define a date range.
- Choose an Event Type (all types are selected by default).
- Choose an Activity Type (all types are selected by default).
- Choose an Action (all actions are selected by default).
- Choose a Status (all statuses are selected by default).
- Optionally, check the Include metadata column to include a column with transactional metadata, such as before/after values, fields changed, and batch items.
-
Select Download CSV to generate the report.
The report is delivered to your local system automatically.
Each audit event includes:
- Date & Time (stored in UTC time offset)
- User (Email) (user email or system@adobe.com)
- Role (User, Admin, or System)
- Activity Type (user-level, admin-level, or system-level)
- Action (e.g., Upload, Share, Delete, Ingest)
- Event Type (Document, Collection, Attribute)
- Asset Name
- Status (Success, Failed, Pending) for processing-related events
- (Optional) Metadata (context such as before/after values, fields changed, batch items, etc.)
For multi-document actions—such as deleting five files—the UI groups the event in a single row while metadata lists each affected document.
