How a RuleCerta audit works
Predictable, inspectable, and safe for production environments. ConnectWise PSA is the currently supported integration.
1. Connect an environment
A workspace can hold several environments — production, test, or one per client. Each environment keeps its own read-only connector credentials (ConnectWise PSA today), connection status, and audit history so tenant data stays isolated.
2. Verify the connection
Before an audit runs, the connection is tested and read access confirmed. Connector credentials are stored encrypted on the server and are never returned to the client UI.
3. Collect the minimum data
We request only the configuration required for the audit — workflow rules with their triggers, events, conditions and actions. Least data, least privilege.
4. Freeze a snapshot
Each completed audit is stored as a fixed snapshot: environment, analysis contract version, analysis engine version, coverage, and findings. Historical audits are not rewritten in place.
5. Analyse deterministically
Versioned structural rules look for enabled workflows without actions or trigger signals, duplicate names, duplicate content, and unmapped-field coverage context.
6. Review, export, repeat
Findings, relationship map, and audit-to-audit comparison in the app; a branded PDF for stakeholders; and evidence-backed history that tracks how findings evolve without modifying the source system.
Audit status lifecycle
An audit is never shown as complete when it is not. Statuses are explicit. Failed audits do not produce a valid report.