Audit and Activity Records
aprity does not have a separate audit console. The records you need for an audit are spread across the aprity app in Salesforce, the web portal, and Salesforce's own setup logs. This page tells you where to look.
Analysis history
Where: the Analyses page of the aprity app in Salesforce.
Each analysis is listed with its date, its status (Pending, Running, Finalizing, Completed, Failed, Cancelled) and its details: language, progress, errors, and a summary of what was analyzed (components, objects documented, business rules, documentation pages). Every completed analysis publishes a new version of the documentation to the web portal.
Use it to show your documentation cadence, for example that documentation was regenerated after a major release.
Documentation versions
Where: in the web portal, Coverage and fidelity > Versions.
Each published version of the documentation stays available, so you can show what the documentation said at a given date. Changes to business rules between versions are listed in the documentation itself.
Fidelity certificate
Where: in the web portal, Coverage and fidelity.
Each version carries a fidelity certificate: a score that measures how much of the documentation was checked against your org's actual configuration, with the scope of that check. It is evidence of how the documentation was verified, not only when it was produced. See Read the Fidelity Certificate.
Human corrections
Where: in the web portal, Human corrections.
Every correction a reader submits on the documentation is kept with its author, date, target, and what the next analysis did with it. Administrators get an additional Moderation mode. This is your evidence of a review process.
Who has access
Where: Salesforce Setup.
- Permission Sets > aprity Admin / aprity User > Manage Assignments: who is an administrator and who is a reader.
- External Client App Manager > aprity > Modify Policies: which profiles can sign in.
- Login History: sign-ins through the aprity app.
- Setup Audit Trail: changes to the External Client App, permission sets and package settings.
See Managing Users and Access.
Correlation IDs
Every response from the aprity API carries a correlation ID in the X-Correlation-Id header, and error responses repeat it in their body. It identifies one request end to end in aprity's service logs.
When you contact support about an error, include the correlation ID if the error message shows one, with the date and time of the error.
What aprity does not keep
- Raw metadata retrieved from your org: deleted when the analysis ends.
- Business records: never read.
- Passwords and secrets: never requested. Secrets and tokens are masked in aprity's service logs.