What it covers
Administrators can preview, save and reset governed layouts for contacts, companies, leads, deals, tickets and projects while required details stay visible.
Customisation and integrations
Record layouts
Choose the supported details and actions shown in core record workspaces.
How it works
Put useful record context in view
Record layouts let an authorised administrator shape supported core record workspaces around the information the team needs most often. The configuration covers defined record families, supported highlight fields, section visibility and quick actions. Required details remain visible, so a shorter workspace does not remove the context people need to identify or handle a record. Layout configuration is separate from changing the record’s data model or granting access. The team can adapt the presentation within the supported contract while each record keeps its own lifecycle and permissions.
In practice
A layout has a version. Saving or resetting checks that version so an older browser cannot silently overwrite a newer administrator’s change. The controls include a preview and a path back to the protected default layout.
When to use it
Useful situations
- Highlight the supported fields staff need before a customer conversation.
- Keep a record workspace focused on the sections relevant to the team.
- Review a layout change before applying it to shared operational work.
A working path
How the work moves
Choose a supported record family
Open Record layouts in Settings and choose the contact, company, lead, deal, ticket or project configuration you need to review. Inspect the current version and the default presentation before deciding which change will improve daily work.
Preview the presentation
Select allowed highlights, section choices and quick actions. Keep identification and required details visible, and check the proposed result with the people who use that workspace. A useful layout should reduce searching without concealing important information.
Save or reset deliberately
Save the reviewed configuration against its current version. If another administrator changed it meanwhile, refresh and compare before trying again. Use the reset control when the protected default is the better fit for the team.
Illustrative scenario
Preparing a contact workspace
A business administrator reviews the supported contact highlights with the account team. They preview a clearer arrangement, retain the required details and save the current version so colleagues can find relationship context more easily.
Before you start
What to check
- Layouts use the supported fields and actions for each record family; they are not a free-form page builder or a permission override.
- Adoption follows the supported record interface. A saved layout contract does not imply that every specialised workspace has the same customisable sections.
Can a layout hide required details?
No. Protected record details remain visible, and highlight fields and quick actions use supported choices.
What happens if two administrators edit at once?
A stale version is rejected. Refresh the current layout and review the difference before saving a new change.
Get started
See your customer work in one place.
Start with the core CRM for free, then add the tools your team needs.