Manage Shared Forms and Record Layouts

Purpose

Presentation definitions let a workspace organize how eligible records are read and edited. Shared storage and assignments keep those definitions manageable across applications.

How It Works

An administrator creates a named definition for a record purpose. Platform stores its document without interpreting the design. Purpose-specific access determines who can read or administer it. An owning application records where the definition is assigned. Changes use version checks and applicable locks. Assigned definitions cannot be removed until their uses are changed. The contact form designer uses shared storage, while the current contact page-layout designer publishes only in its browser.

Relationships

Record eligibility determines which definitions may be created. Assigning applications retain responsibility for selecting and rendering them.

Show evidence (sources, provenance, origins, pinned commits)

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Outcomes: Presentation definitions let a workspace organize how eligible records are read and edited.Assigned definitions cannot be removed until their uses are changed.
Surfaces: consoleapi
Preconditions: The target supports the relevant presentation capability or is a live custom object.
Intent sources: services-platform:docs/layouts.md#2. The purpose is the authorizationservices-platform:docs/layouts.md#4a. Two console forms (Andrew, 2026-10-11: create and edit forms)services-platform:docs/standards/custom-field-capability.md#4. What enabling custom fields requires (console and portal forms and layouts)services-platform:docs/proposals/custom-objects/09-decisions.md#D-09 (custom object purposes share Platform keys)

Controls

25 controls apply, from the corpus control catalogue.

TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-CRY-001 TC-CRY-002 TC-CRY-003 TC-CRY-004 TC-DAT-001 TC-DAT-003 TC-DAT-004 TC-LOG-004 TC-LOG-005 TC-PI-001 TC-PI-003 TC-PI-005 TC-PRV-001 TC-PRV-002 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-TEN-004 TC-VEN-001 TC-VEN-002 TC-VEN-003

Permissions

Key	Checked at	Scope
`platform.layouts.read`	api	tenant
`platform.layouts.create`	api	tenant
`platform.layouts.update`	api	tenant
`platform.layouts.delete`	api	tenant
`crm.contact-layouts.read, .create, .update, .delete and the other purpose owners' administration keys`	service	tenant
`crm.contacts.read, crm.organizations.read, committees.committees.read, platform.custom-records.read (consumption)`	service	tenant
`platform.custom-objects.read, .create, .update, .delete (administration of custom object purposes)`	service	tenant

Business Rules

13 rules, 11 to be proved before approval. A rule's product intent is derived from its origin: 13 confirmed by a product decision, the rest inheriting this capability's confirmed.

Id	Rule	Kind	Enforced at	Provenance
`01`must prove Confirmed	A presentation definition stores a trimmed name of one to two hundred characters, optional description, fixed purpose and an opaque JSON object of at most 256 kibibytes that is returned without interpretation. proved by `ATS-PFM-MTD-008-01`, `TST-PFM-MTD-098`	validation	api, service, database	test services-platform:modules/layouts/tests/integration/services/persistence/console-page-layouts.integration.spec.js#refuses a layout larger than the stated maximum, telling the person the limit and the size
`02`must prove Confirmed	A replacement or patch cannot change the purpose and reports the stored and requested purposes when they differ. proved by `ATS-PFM-MTD-008-02`, `TST-PFM-MTD-087`, `TST-PFM-MTD-098`	invariant	service	test services-platform:modules/layouts/tests/integration/services/persistence/console-page-layouts.integration.spec.js#refuses a replacement that names another purpose, naming both the stored one and the request’s
`03`must prove Confirmed	Reading accepts the purpose administration read key or record consumption key, while writes require the appropriate purpose administration key defined by the record owner. origin: services-platform:docs/layouts.md#2. The purpose is the authorization proved by `ATS-PFM-MTD-008-03`, `TST-PFM-MTD-087`	permission	api	test services-platform:modules/layouts/tests/e2e/console-page-layouts-api.e2e.spec.js#answers 403 to a caller who may read contacts but not administer their layouts
`04`must prove Confirmed	Unreachable definitions return not found for reads and writes, disappear from lists and produce an empty purpose-filtered list. origin: services-platform:docs/layouts.md#What a refused caller is told proved by `ATS-PFM-MTD-008-04`, `TST-PFM-MTD-087`	permission	api	test services-platform:modules/layouts/tests/e2e/console-page-layouts-api.e2e.spec.js#answers 404 for a definition of a purpose the caller may not read, rather than confirming it exists
`05`must prove Confirmed	Creation rejects an unregistered purpose before purpose permission evaluation, and a Platform staff wildcard cannot substitute for the purpose owner keys. proved by `ATS-PFM-MTD-008-05`, `TST-PFM-MTD-087`	validation	api	test services-platform:modules/layouts/tests/e2e/console-page-layouts-api.e2e.spec.js#answers 400 for a purpose this build does not register, naming it
`06`must prove Confirmed	Custom-object purposes use shared definition administration and record-read keys, require a draft or active object in the workspace and become unreadable when that object is archived. origin: services-platform:docs/proposals/custom-objects/09-decisions.md#D-09 proved by `ATS-PFM-MTD-008-06`, `ATS-PFM-MTD-008-12`, `TST-PFM-MTD-088`	permission	api, service	test services-platform:modules/layouts/tests/e2e/custom-object-forms.e2e.spec.js#answers 404 for a stored form once its custom object is archived
`07`must prove Confirmed	Replacement and patch require the current version, update locks block modifications and delete locks block removal. proved by `ATS-PFM-MTD-008-07`, `TST-PFM-MTD-098`	validation	service	test services-platform:modules/layouts/tests/integration/services/persistence/console-page-layouts.integration.spec.js#refuses the version the caller did not read, as a StaleObject
`08`must prove Confirmed	Definition lists default to fifty entries, cap at two hundred, order by name and use a cursor that is rejected when malformed. proved by `ATS-PFM-MTD-008-11`, `TST-PFM-MTD-087`	policy	api, service	test services-platform:modules/layouts/tests/e2e/console-page-layouts-api.e2e.spec.js#answers 400 for a ?cursor= it did not issue
`09`must prove Confirmed	The owning save registers presentation use in five assignment slots, whose database references reject missing definitions or mismatched workspace, kind or purpose. proved by `ATS-PFM-MTD-008-08`, `TST-PFM-MTD-093`	invariant	database	test services-platform:modules/layouts/tests/integration/db/layout-assignments.table.integration.spec.js#refuses an assignment naming a definition of the wrong kind, because each slot’s column references one table
`10`must prove Confirmed	Create and edit assignments may select either two different console forms or the same console form. origin: services-platform:docs/layouts.md#4a. Two console forms (Andrew, 2026-10-11) proved by `ATS-PFM-MTD-008-09`, `TST-PFM-MTD-093`	policy	database	test services-platform:modules/layouts/tests/integration/db/layout-assignments.table.integration.spec.js#holds a different console form for creating a record and for editing one, each under its own column
`11`must prove Confirmed	An assigned definition cannot be deleted until its referring records or settings are changed, and concurrent assignment and deletion cannot leave an invalid reference. proved by `ATS-PFM-MTD-008-10`, `TST-PFM-MTD-087`, `TST-PFM-MTD-093`, `TST-PFM-MTD-098`	invariant	service, database	test services-platform:modules/layouts/tests/integration/services/persistence/console-page-layouts.integration.spec.js#names every referring row, in a stable order, when more than one assigns it
`12` Confirmed	The contact form designer persists console forms in Platform and reports unsupported content when opening a stored form rather than discarding it. origin: services-platform:docs/milestones/PLAT-M5-custom-records.md#PLAT-M5 D17 (FormEngine forms)	policy	console	observed react-console:lib/forms/storage/console-forms.ts:readStoredForm
`13` Confirmed	The contact page-layout designer stores drafts and published layouts in browser storage instead of Platform presentation storage.	policy	console	observed react-console:lib/layout-designer/persistence.ts:publishLayout

Scenarios

Id	Given	When	Then	Provenance
`01`	A contact type and default settings both assign the same layout.	Try deleting that layout before and after clearing its assignments.	The initial refusal identifies both uses; deletion succeeds after their removal.	documented services-platform:docs/layouts.md#5. Deleting a definition

Edge Cases

Id	Given	When	Then	Provenance
`02`	A caller can read contacts but cannot administer their layouts.	Read a layout and attempt to edit it.	Reading succeeds while the edit receives a forbidden response.	test services-platform:modules/layouts/tests/e2e/console-page-layouts-api.e2e.spec.js#answers 403 to a caller who may read the definition but not administer it

Planning

Implementation

Manage Shared Forms and Record Layouts ​

Purpose ​

How It Works ​

Relationships ​