Source: https://nishanth-fern-test.docs-staging.pageloop.ai/web/gxp-compliance-ready

# GxP Compliance Ready

Whatfix is GxP **Compliance** **Ready**, providing capabilities that help enterprises manage content in regulated environments through controlled publishing, electronic signatures, audit trails, and change traceability. Whatfix’s GxP compliance layer helps compliance and quality teams manage in-app guidance without compromising a validated environment.

For example, during an audit at a pharmaceutical organization, the auditor asks to see every change made to a Whatfix Flow in the past year. Without a central record of changes, the team must search through emails and spreadsheets to find this information. With Whatfix's GxP compliance capabilities, every publish or unpublish action includes a Change Request ID, such as a Jira ticket, and a verified user identity. Whatfix records each action in the Audit Logs, so the team can show the auditor who changed the Flow, when, and why.

See the following articles to learn more about GxP capabilities in Whatfix:

- [Audit Logs captured by Whatfix](/web/audit-logs-captured-by-whatfix-app)
- [GxP Compliance Ready: Re-Authentication for Publish and Unpublish content](https://support.whatfix.com/studio/docs/gxp-compliance-ready-re-authentication-for-publish-and-unpublish-p2p)

---

#### Benefits of GxP Compliance

Whatfix's GxP compliance provides the following benefits:

- Maintains data integrity by ensuring information remains accurate, complete, and traceable.
- Strengthens change control by ensuring changes follow defined review and approval processes.
- Improves audit readiness by maintaining clear records of relevant activities and decisions.
- Protects the validated environment by controlling changes before they reach production.
- Supports global compliance by helping organizations align processes with applicable GxP requirements.

GxP refers to the Good Practice requirements that apply to regulated industries, such as Life Sciences and Pharmaceuticals. These requirements help organizations maintain data integrity, controlled processes, validated systems, and traceable changes throughout the content and system lifecycle.

A unique identifier for the change, typically linked to your change management system (for example, Jira). It helps track and validate that the update is approved.
