How to Generate Compliance-Ready Documentation
aprity can generate documentation formatted for compliance audits, security reviews, and regulatory requirements. This guide explains how to configure a scan for compliance-ready output.
Prerequisites
- Professional or Enterprise plan.
- At least one completed scan is recommended before generating compliance documentation.
Steps
- Open the aprity app in Salesforce.
- Navigate to the Generate tab.
- Select the PDF output format. PDF is the recommended format for compliance deliverables.
- Optionally, also select DOCX if your compliance team requires editable documents.
- Configure other scan options (language, metadata scope).
- Click Generate to start the scan.
info
On Enterprise plans, the Global Analysis feature is automatically enabled. This adds cross-object dependency analysis and a security baseline to the output, which are valuable for compliance reviews.
What Compliance Documentation Includes
aprity-generated documentation covers several areas relevant to audits:
- Security Baseline -- permission sets, profiles, and field-level security analysis
- Access Catalog -- who has access to what, mapped across profiles and permission sets
- Automation Inventory -- complete list of triggers, flows, validation rules, and their purposes
- Dependency Map -- how objects and automations relate to each other
- Data Model -- object relationships, field types, and constraints
Tips for Audit Preparation
- Run a fresh scan shortly before the audit to ensure documentation reflects the current state of the org.
- Use the PDF format for formal submissions and DOCX for internal review.
- Schedule recurring scans to maintain an up-to-date compliance baseline. See How to Schedule Recurring Scans.
tip
Combine aprity documentation with your org's change management records for a complete audit trail. aprity documents the current state; your change management process documents the history.