Integrations

• Permit authority or register. Agree where the permit reference on a site check points and how inspectors confirm the current source record.
• Document repository. Set a stable location for evidence references used in control tests and for controlled document source references.
• Identity service. Map signed-in users to active team members and the right organization before assigning records.
• Report sharing. Agree how the team will distribute the reports it prepares and who may receive them.

These are connections to plan for a rollout. The app’s site check, test and document records provide the references and operating context. Your team chooses each external service and its access rules.

Choose an owner for each connection and test how a changed or unavailable source is handled. A reference is useful only when the intended reviewer can open the right evidence. Keep operation keys and receipts for retried work, inspect failed attempts from Operations Overview and reconcile any unknown outcome before repeating an external action. Do not turn a source system’s unavailable response into an assumed approval.