---
id: ADR-PFM-SEC-011
title: No custom-field capability
product_area: platform
module: security
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
decision: Retain the approved default of no custom fields for customer, workspace and security records; no
  enabling object registration is present and their screens use dedicated shared components.
constrains:
- DOM-PFM-SEC-001
- DOM-PFM-SEC-002
- DOM-PFM-SEC-003
- SVC-PFM-SEC-customers
- SVC-PFM-SEC-tenants
- SVC-PFM-SEC-security
origin: 'R2-ARCH-001 §2 classification (Andrew, 2026-10-19): every other app has none until Andrew designates
  one (services-platform:docs/standards/custom-field-capability.md)'
alternatives:
- option: Enable custom fields for commercial or workspace attributes.
  why_not: The existing classification does not designate these records, so enabling them requires Andrew’s
    separate product decision.
consequences:
- Absence of a custom-field enabling declaration means the capability is off under the cited standard.
- The observed screens are dedicated components rather than registered configurable forms or page layouts.
supersedes: []
evidence:
- 'services-platform at ad3f6a65: the records named in origin and the code cited by the constrained artifacts'
examined_at: '2026-10-23'
examiner: codex
---

# No custom-field capability

## Context

The custom-field classification already governs these records. The implementation has no enabling registration in this module; the examination does not invent a capability declaration.

A future designation must follow the existing product-decision and registration process.

## Decision

Retain the approved default of no custom fields for customer, workspace and security records; no enabling object registration is present and their screens use dedicated shared components.

## Alternatives Considered

Enable custom fields for commercial or workspace attributes. The existing classification does not designate these records, so enabling them requires Andrew’s separate product decision.

## Consequences

Absence of a custom-field enabling declaration means the capability is off under the cited standard.

The observed screens are dedicated components rather than registered configurable forms or page layouts.