---
id: ADR-MBR-STR-009
title: Apply Custom-Field Opt-In to Units
product_area: membership
module: structure
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-membership: 5994c270e8a37a30f848e99ba5b5ee6b87c08893
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  Organizational units declare Platform's shared custom-field capability, while the other structural and
  configuration records have no such declaration.
constrains:
  - DOM-MBR-STR-001
  - DOM-MBR-STR-002
  - DOM-MBR-STR-003
  - DOM-MBR-STR-004
  - DOM-MBR-STR-005
  - DOM-MBR-STR-006
  - RESP-MBR
origin: >-
  R2-ARCH-001, Andrew 2026-10-19 (organizational units declare custom fields): services-
  membership:AGENTS.md#Custom Fields Are Opt-In Per Entity: R2-ARCH-001 (Andrew, 2026-10-19)
alternatives:
  - option: Enable custom fields on additional configuration records.
    why_not: No cited designation authorizes those entities; extending capability requires Andrew's decision.
  - option: Store unit extras through a bespoke field mechanism.
    why_not: The cited standard requires the shared definition and value-storage mechanism for designated entities.
consequences:
  - 'Single-unit and query reads expose custom values, while ordinary lists and tree reads omit them.'
  - >-
    Custom fields, configurable forms and page layouts are distinct registration capabilities; this record
    does not decide a future screen layout.
  - Adding a designated entity requires a product record and corresponding metadata opt-in.
supersedes: []
evidence:
  - >-
    services-membership at 5994c270: modules/structure/metadata/structure.objects.ts (customFields true on
    units); modules/structure/db/organizational-unit-custom-field-values.table.ts
---

# Apply Custom-Field Opt-In to Units

## Context

Associations need customer-defined information on units. The recorded standard specifies which entities can opt in and how values are governed.

## Decision

This record applies the existing unit designation. Its metadata registration declares shared custom fields and separate configurable form and layout capabilities without implying those screens already exist.

## Alternatives Considered

Enable custom fields on additional configuration records. No cited designation authorizes those entities; extending capability requires Andrew's decision. Store unit extras through a bespoke field mechanism. The cited standard requires the shared definition and value-storage mechanism for designated entities.

## Consequences

Single-unit and query reads expose custom values, while ordinary lists and tree reads omit them. Custom fields, configurable forms and page layouts are distinct registration capabilities; this record does not decide a future screen layout. Adding a designated entity requires a product record and corresponding metadata opt-in.