---
title: 8. Read-only Fields
slug: docs/8-read-only-fields
docTags: 
createdAt: 2026-06-08T08:21:38.592Z
---

Certain field categories are always rendered as read-only in the edit forms. Edits to these fields are blocked to prevent corruption of the profile's identity graph or system metadata.

## Identity fields

Any field defined as an identity descriptor in the XDM schema — for example:

- ECID
- Email (when used as an identity)
- CRM ID
- Loyalty ID

Modifying identity fields through the Streaming Inlet could create duplicate or unresolvable profiles in the identity graph.

## System fields

AEP-managed metadata fields that are set by the platform and cannot be overridden via streaming ingestion — for example:

- \_id
- timestamp
- createdAt
- modifiedAt
- Internal merge policy references

## Behaviour in forms

Read-only fields are visible in the dynamic form for reference and context, but their inputs are disabled. They are **not included** in the outgoing JSON patch even if they appear in the payload preview.

:::BlockQuote
ℹ️ Read-only status is determined by the XDM schema definition, not by the tool itself. Any field with an identity or system descriptor in the schema will always be locked.
:::