Configuration Audit

The Configuration Audit is a report that flags configuration anomalies in your Salesforce org. It surfaces patterns that are easy to miss when reviewing automations and permissions one component at a time -- for example, automations that trigger one another in a cycle, or profiles that carry far more access than their users appear to need.

The report is generated as part of a scan and read in the Customer Portal. It is built on top of aprity's deterministic analysis of your org, with one additional LLM narration pass per scan to explain each finding in plain language.

What it flags

The Configuration Audit highlights anomalies such as:

• Execution / automation cycles. Chains of triggers, flows, and other automations that invoke one another in a loop -- a common source of recursion, hard-to-debug behaviour, and governor-limit failures.
• Over-permissioned profiles. Profiles that grant broad access (object CRUD, field-level security, administrative permissions) out of proportion to what the profile's purpose suggests.

Each finding is explained in business-readable terms and traced back to the source metadata so an admin can act on it.

How it works

1. During a scan, aprity builds its deterministic analysis of automations, execution order, and access.
2. The Configuration Audit step inspects that analysis for the anomaly patterns above.
3. A single LLM narration pass turns the detected anomalies into a readable report with explanations.
4. The report is available in the portal alongside the rest of the scan output.

Because the detection is deterministic and only the explanation is LLM-generated, the findings are grounded in your actual metadata rather than guessed.

Plan availability

The Configuration Audit is available on the Intelligence plan only. It is not included on Documentation or Trial.

Plan	Configuration Audit
Documentation	Not included
Trial	Not included
Intelligence	Included

The audit adds one extra LLM narration call per scan, which is why it is gated to Intelligence for LLM-cost control. See Plan Comparison for the full feature matrix.

note

The feature is fail-closed: if the plan check cannot be confirmed for a scan, the Configuration Audit step is skipped for that scan rather than running by default.

When to use it

• You are preparing a health check or technical-debt review of an org.
• You suspect recursive automation behaviour and want to see the cycles laid out.
• You are tightening security and want a quick list of profiles that look over-permissioned.
• You are onboarding a new admin who needs to understand the org's risk areas.

For anything else, contact support@aprity.ai.