Docs: Organize Layout for CRM field groups (CRMAAS-3083)

[haleyserrano]

JIRA

CRMAAS-3083 — Create the Organize Layout page

Classification

UI/UX change — new admin configuration page for arranging CRM field layout.

Repo targeted

Business App (end-user facing) — this feature is reached via Administration → CRM Objects inside Business App itself, alongside the existing custom fields manager.

Summary of documentation updates

Documented the new Organize Layout page in the existing CRM Objects admin article:

• New "Organize field layout" section explaining how to open the page and what it lets you do (arrange fields into groups, set field order within a group, set sort order for unassigned fields, reset to default)
• Added a bullet to the "What's included" list referencing the new capability

Existing docs updated vs. new docs created

Updated existing docs only — no new page created.

Placement reasoning

docusaurus/docs/business-app/administration/crm-objects/index.mdx is the existing article for the CRM Objects administration area (Contacts, Companies, Opportunities, custom objects, and their custom fields). Organize Layout is a new capability within that same admin area, so it was added as a new section there rather than a standalone page.

Acceptance criteria coverage

The ticket contains a single description line (no itemized acceptance criteria in JIRA): "Build the Organize Layout configuration page where admins arrange field groups, order fields, and set the unassigned sort order for a CRM object type, backed by the GetFieldLayout / UpsertFieldLayout / ResetFieldLayout APIs." All three user-facing capabilities described (arrange field groups, order fields, set unassigned sort order) are covered in the new section. Internal API/RPC names were intentionally omitted from the user-facing doc.

Figma / images

None were provided with this ticket. No screenshots were added — flagging this as a follow-up opportunity once the feature is available to add a screenshot.

Skills used

pre-push-validation (frontmatter, tag-closure, and gray-label checks passed on the modified file).

Assumptions / limitations

• The parent epic (CRMAAS-3081, "Field Layout") is still in To Do status, even though this story and its sibling (CRMAAS-3082) are Done. The only other open sibling ticket (CRMAAS-3084) extends field layout into account templates — it's an additive feature, not a gating/eligibility/feature-flag ticket, and the epic has no Product-Roadmap label. Proceeding on that basis, but flagging the epic's incomplete status here per the rollout-check step.
• Could not confidently identify the PR reviewer: no GitHub PRs are linked to this JIRA ticket, and this session's GitHub access doesn't extend to the code repo. Not tagging a code-author reviewer to avoid mis-tagging someone outside the org.
• No source material (Figma, ticket detail) specifies the exact UI copy for buttons/labels beyond "Organize Layout" (from the ticket title) — wrote the navigation steps generically and consistent with this doc's existing style for the CRM Objects area.

@ahnikakuse @haleyserrano @maryam6samadi

---

Generated by Claude Code