Make Custom Records Discoverable

Purpose

Staff need recognizable entry points for the organization own record types. Placement and custom apps group those entry points within the console.

How It Works

An administrator selects an existing app or defines a custom app. An object placement may include a navigation group. The object can also remain without app placement. The console requests navigation for the current staff member. Platform includes the active objects that person can read and the apps containing them. A custom app cannot be archived while live object placements depend on it. Placement provides a location to work; the corresponding permissions still determine access.

Relationships

Object definitions hold placement. Record access filters navigation, and relationship cards provide another route to unplaced records.

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: Staff need recognizable entry points for the organization own record types.A custom app cannot be archived while live object placements depend on it.
Surfaces: consoleapi
Intent sources: services-platform:docs/milestones/PLAT-M5-custom-records.md#PLAT-M5 D9 (placement), D15 (custom apps), B2, B3, B4services-platform:docs/milestones/plans/PLAT-M5-plan.md#2. Andrew's placement direction; PLAT-M5-S01, S13services-platform:docs/proposals/custom-objects/09-decisions.md#D-14 (the administrator chooses an area)

Controls

27 controls apply, from the corpus control catalogue.

TC-AI-001 TC-AI-002 TC-AI-003 TC-AI-004 TC-AI-006 TC-AI-007 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-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.custom-objects.read`	api	tenant
`platform.custom-objects.create`	api	tenant
`platform.custom-objects.update`	api	tenant
`platform.custom-objects.delete`	api	tenant
`platform.custom-records.read`	api	record

Business Rules

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

Id	Rule	Kind	Enforced at	Provenance
`01`must prove Confirmed	Placement accepts the seventeen console navigation apps or a workspace unarchived custom app and an optional trimmed group of one to one hundred characters, rejecting unknown apps. origin: services-platform:docs/milestones/PLAT-M5-custom-records.md#PLAT-M5 D9 (Andrew, 2026-10-19) proved by `ATS-PFM-MTD-010-01`, `TST-PFM-MTD-067`, `TST-PFM-MTD-074`	validation	service	test services-platform:modules/custom-objects/tests/integration/services/persistence/custom-objects.integration.spec.js#refuses an app that is neither an application nor a custom app, naming it, and writes nothing
`02`must prove Confirmed	An object can be created, activated and used without placement or ownership, remaining accessible through links and queries. origin: services-platform:docs/milestones/PLAT-M5-custom-records.md#PLAT-M5 B4 (Andrew, 2026-10-19: "Allow neither") proved by `ATS-PFM-MTD-010-02`, `TST-PFM-MTD-013`, `TST-PFM-MTD-067`	policy	service	test services-platform:modules/custom-objects/tests/integration/services/persistence/custom-objects.integration.spec.js#activates an object that has neither a placement nor an owner association type (B4: no activation rule for either)
`03`must prove Confirmed	A custom app has a permanent nonreserved key, bounded label, icon and order from zero to ten thousand, supports archival and restoration instead of deletion and uses versioned replacement. origin: services-platform:docs/milestones/PLAT-M5-custom-records.md#PLAT-M5 D15 (Andrew, 2026-10-19: "Build in PLAT-M5") proved by `ATS-PFM-MTD-010-03`, `TST-PFM-MTD-049`, `TST-PFM-MTD-060`	validation	service, database	test services-platform:modules/custom-objects/tests/integration/services/persistence/custom-apps.integration.spec.js#refuses the key of a platform application, which a placement could not tell from it
`04`must prove Confirmed	App archival is refused while draft or active objects are placed there, naming those objects; archived objects may retain the placement. origin: services-platform:docs/milestones/PLAT-M5-custom-records.md#PLAT-M5 B3 (Andrew, 2026-10-19: "Refuse, name objects") proved by `ATS-PFM-MTD-010-04`, `ATS-PFM-MTD-010-07`, `TST-PFM-MTD-049`, `TST-PFM-MTD-060`	validation	service	test services-platform:modules/custom-objects/tests/integration/services/persistence/custom-apps.integration.spec.js#refuses to archive an app while a draft and an active object are placed in it, naming both, and leaves the app unchanged
`05`must prove Confirmed	An archived app rejects new placements and replacements until it is restored. proved by `ATS-PFM-MTD-010-05`, `TST-PFM-MTD-060`, `TST-PFM-MTD-067`	validation	service	test services-platform:modules/custom-objects/tests/integration/services/persistence/custom-objects.integration.spec.js#refuses a new placement in an archived custom app, and writes nothing
`06` Confirmed	Custom-app counts remain unrestricted pending the product-wide limits mechanism. origin: services-platform:docs/milestones/PLAT-M5-custom-records.md#PLAT-M5 B2 (Andrew, 2026-10-19: deferred)	policy	service	test services-platform:modules/custom-objects/tests/integration/services/persistence/custom-apps.integration.spec.js#accepts the tenant’s twenty-first app and lists all twenty-one (Andrew’s B2: no limit until the app-wide limits mechanism)
`07` Confirmed	App reads include placed active objects with their groups and staff access and omit draft or archived objects.	calculation	service	test services-platform:modules/custom-objects/tests/e2e/custom-apps.e2e.spec.js#leaves a draft object placed in the app out of its objects
`08`must prove Confirmed	Navigation includes only readable active objects and apps containing them, respects object-scoped roles and refuses callers with no record-read reach. origin: services-platform:docs/milestones/PLAT-M5-custom-records.md#PLAT-M5 D10, D15 proved by `ATS-PFM-MTD-009-13`, `ATS-PFM-MTD-010-06`, `ATS-PFM-MTD-010-07`, `TST-PFM-MTD-051`	permission	api, service, console	test services-platform:modules/custom-objects/tests/e2e/custom-object-records.e2e.spec.js#answers a role scoped to custom_object:boat the boats alone
`09`must prove Confirmed	Reset preserves custom apps and object placements, whereas workspace deletion removes them. origin: services-platform:docs/milestones/PLAT-M5-custom-records.md#PLAT-M5 D7 (Andrew, 2026-10-19: "Keep types") no proof recorded yet	lifecycle	service	documented services-platform:docs/custom-objects.md#Tenant lifecycle

Scenarios

Id	Given	When	Then	Provenance
`01`	Boat belongs to the Marina custom app.	Open the console as a boat reader.	The app menu offers Marina with Boats beneath it.	test react-console:acceptance/custom-objects/playwright/journeys/PLAT-M5-S01.spec.ts#PLAT-M5-S01: an administrator creates Boat in a new app, owned by Contact, and Marina > Boats appears

Edge Cases

Id	Given	When	Then	Provenance
`02`	Contact ownership is configured for Boat but no app placement exists.	Find the boats through the owner record.	The contact page provides access without a Boats menu entry.	test react-console:acceptance/custom-objects/playwright/journeys/PLAT-M5-S13.spec.ts#PLAT-M5-S13: a boat placed only on contacts has no menu entry and is reached from the contact's page

Planning

Implementation

Make Custom Records Discoverable ​

Purpose ​

How It Works ​

Relationships ​