> ## Documentation Index
> Fetch the complete documentation index at: https://docs.elementum.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Compliance Profiles

> Define named, versioned sets of compliance controls in Settings and apply them to Apps, Elements, and Tasks for regulated requirements such as GxP.

Compliance Profiles let Org Admins define named, versioned sets of compliance controls in Settings and reuse them across the platform. Apply one or more profiles to an App, Element, or Task under Security so regulated customers can govern just the objects that need it. When multiple profiles are applied to the same object, their controls combine.

***

## Required Reason for Change

Required Reason for Change is a Compliance Profile control. When it is applied to an App, Element, Task, or Transaction, users must enter a written reason on every edit to records in that object. The reason is saved alongside the before and after values in the record's Activity log.

On regulated objects, the Save modal lists each pending change for review before the save completes. Updates coming from automations, imports, list views, and the data entry grid are rejected.

***

## Workflow Change Request

Workflow Change Request is a Compliance Profile control. When it is added to a profile and that profile is applied to an App in a protected environment such as Production, deployments into that environment require an approved change request before they can proceed.

Org Admins configure separate approval processes for Major and Minor changes. Every request is recorded in the deployment history with its requester, reason, approval steps, and decisions.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.