Practical guides for people who have to understand an org.
How to document a Flow, how to find everywhere a field is really used, what an auditor asks of a Salesforce org. Written for the work itself — including the parts of the answer that have nothing to do with aprity.
Start here
Each one answers its question first — the native tooling, its real limits, and the manual method — before it says where aprity fits.
How to document a Salesforce Flow
Flow Builder shows you the canvas. It does not tell you what the Flow changes, what it depends on, or what breaks when you edit it — and those are the three things anyone reading the documentation actually needs.
How to find everywhere a Salesforce field is used
Salesforce will tell you most of the places a field is referenced. The dangerous part of the answer is the remainder — the references no static check can see, which is exactly where deletions go wrong.
Preparing a Salesforce org for an ISO 27001 audit
The certificate is for your information security management system, not for your org. What the auditor wants from Salesforce is narrower and more awkward: evidence that access, change and logging work the way your policy says they do.
What aprity does about each of these
The guides stay out of the sales conversation. These pages are the sales conversation.
Automated Salesforce documentation
Every object, flow, rule and dependency documented in business language, current with every scan.
See the pageSalesforce impact analysis
Pick a component and a change type; get the downstream blast radius computed from the dependency graph.
See the pageSalesforce org audit
A verifiable, source-traceable baseline for ISO 27001, SOC 2 and HDS preparation.
See the pageSelligent to Salesforce migration
Document a legacy Selligent CRM read-only and turn it into a grounded migration backlog.
See the pageOr stop reading about it and look at your own org.
A free 14-day evaluation, read-only, no credit card. You review the output before deciding anything.