Enterprise Integration: Connected Assurance Without Losing Control

Integration should extend control, not bypass it

A technically successful connection is not automatically a controlled connection. Every integration needs a defined business purpose, an accountable owner, an approved environment and only the permissions needed for that use.

RPG Excellence therefore separates API access from normal portal access. Granting an integration permission does not change a person's application role, subscription entitlement or administrative authority.

• Keep test and live credentials separate.
• Issue credentials for a named purpose and organisation.
• Apply least-privilege permissions by information domain.
• Review, expire and revoke access when the purpose changes.

One credential does not mean access to everything

The RPG Excellence API uses granular read permissions for findings, internal audits, CAPA-8D cases, assets, suppliers and Company Users. An integration receives only the scopes selected for it and can access records belonging to its authorised organisation.

This makes the boundary explainable to management, auditors and customers: which system can see which information, why it needs that information and how access can be withdrawn.

• findings:read for controlled finding summaries
• audits:read for internal-audit programme and status information
• capa:read for CAPA-8D case status and severity
• assets:read for asset criticality and PPM status
• suppliers:read for approved-supplier and review information
• people:read for the controlled Company User directory

What can now be connected

The first API release is deliberately read only. It supports controlled reporting and analysis without allowing an external system to change the underlying assurance record.

Typical uses include an executive dashboard showing overdue actions, a maintenance view identifying critical assets with overdue PPM, a supplier review report and a consolidated position across findings, audits and CAPA-8D.

A practical management example

An organisation wants its business-intelligence platform to present a weekly assurance overview. The integration is created in the test environment, assigned read access to findings, audits, CAPA-8D and assets, and validated using filtered and paginated requests.

Once the output and organisational boundary are confirmed, a separate live credential can be approved. Leaders receive a current view while the authoritative records, workflow decisions and evidence remain controlled in RPG Excellence.

What the API deliberately does not expose

Controlled integration also requires clear exclusions. The interface is not intended to expose passwords, authentication tokens, invitation-security metadata, unrestricted private evidence, records from another organisation or administrative functions outside the approved scope.

The full API secret is displayed only when created. RPG Excellence retains a protected digest for verification, records integration activity and allows the credential to be revoked without changing the user's portal permissions.

Start read only and prove the boundary

A sensible implementation begins with the health endpoint, then one information domain, narrow filters and a test credential. The organisation should verify the response structure, pagination, permitted records, logging and revocation before expanding the scope.

Write operations should only follow a separate control design covering validation, approval, conflict handling, evidence integrity and rollback. They are not part of the current read-only release.

The next step: controlled notification

A future phase may add governed webhooks so approved systems can be notified when significant assurance events occur. That capability must include signed events, retry controls, delivery history and carefully defined payloads.

Until then, consumers should use proportionate scheduled requests and retain their own evidence of how imported information is used.

How RPG Excellence supports the control

RPG Excellence Enterprise Integration provides organisation-scoped, read-only API access to findings, internal audits, CAPA-8D, assets, suppliers and Company Users, supported by granular permissions, test and live environments, expiry, activity records and immediate revocation.