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

# CRM: identity reference context updated

> The public documentation now reflects CRM-related identity context from the May API reference audit.

<Badge stroke icon="calendar-days" iconType="regular">May 4, 2026</Badge> <Badge stroke icon="file-code" iconType="regular">Documentation update</Badge> <Badge color="purple" size="lg" stroke icon="eye" iconType="regular">Review recommended</Badge>

## Affects

***

Teams reading CRM documentation alongside identity-related API reference pages in the public portal.

This update applies to the public documentation portal. It does not change the runtime API behavior.

<Note>
  The public documentation portal is the customer-facing reference. Repository source files should not be treated as integration artifacts or downloaded API specifications for client use.
</Note>

## What changed

***

### CRM documentation context

CRM was included in the May API reference audit because the affected documentation touches identity-related reference context used across the public portal.

The CRM pages remain focused on holder and alias account concepts. The related identity documentation now has clearer Access Manager coverage for MFA, providers, and application-provider links.

## Impact

***

This is a documentation update. No CRM runtime behavior changed.

Teams reviewing CRM together with identity configuration should use the updated documentation portal for the current public portal view.

## What you need to do

***

<Steps>
  <Step>
    Review CRM documentation together with the updated identity reference pages if your implementation depends on both areas.
  </Step>

  <Step>
    Do not treat repository source files as client integration artifacts. Use the documentation portal as the customer-facing reference.
  </Step>
</Steps>

### Deadline

None.

### Why

The May audit touched CRM-adjacent identity context. Keeping CRM visible as its own release note avoids hiding it behind another product tag.

## Resources

***

* [CRM overview](/en/midaz/crm/crm-overview)
* [CRM error list](/en/reference/midaz/crm/crm-error-list)