Every object has a page for each of its records. Until you change it, the page has the same tabs everywhere: Overview (the fields), Relations, Notes, Tasks and Timeline. The owner and administrators can arrange it differently for each object, and everyone who can open the object sees the result.
Edit the layout
Open Settings, then Data model, choose an object and open the Layout tab. On a record page, owners and administrators also get an Edit layout button that leads there.
- Tabs - add, rename, reorder and delete tabs. A layout has up to 12.
- Sections - a tab holds sections, each with an optional heading. A tab has up to 20.
- Widgets - a section holds widgets, up to 30. Move them up and down, and open a widget to change its settings.
The editor shows a preview of the arrangement next to the list. Save layout makes it the page for everyone, Discard changes goes back to what is saved, and Reset to default returns the object to the standard tabs.
Widgets
| Widget | What it shows |
|---|---|
| Group of fields | Either every field of a kind (fields, built-in fields, record details; a field you add later shows up by itself) or the fields you choose, in the order you choose. |
| Single field | One field. |
| Text | Formatted text of your own, such as instructions or a reminder. Up to 20,000 characters. |
| Related records | The records linked through one relation, or through every relation, as tables. |
| Notes, Tasks, Timeline, Files | The record's notes, tasks, history, and the files in its file fields. Each can be used once in a layout. |
| Embedded page | A page from another site, shown inside the record. |
| Chart | One of your dashboard widgets, limited to the records linked to this record: the value of a company's deals, the open tasks of a project. |
Fields a person's role cannot see are left out of the page for that person without a trace, and so are relations they cannot open. A field that was deleted or switched off disappears from the layout; it comes back if you switch it on again.
Embedded pages
An embedded page needs a full https address of another site. Addresses of our own site,
local and private addresses, addresses with a user name or password, and anything that is not https
(http:, javascript:, data:) are refused when you save. The page is shown in a sandbox: it may
run its own scripts, forms and pop-ups, it cannot reach Formspring, it is sent no referrer, and it
is given no access to the camera, microphone or location. A site decides for itself whether it
allows being shown inside another page; some do not.
Administrators of a self-managed installation can limit which sites may be embedded with the
CRM_LAYOUT_IFRAME_HOSTS setting (a list of hosts; their subdomains are allowed too).
Earlier versions
Each save is a new version, and the last 20 are kept. Owners and administrators can see them and put one back through the API (a restored version is saved as a new one). Resetting to the default keeps the layout you had among the versions.
In the API and for agents
GET /crm/objects/{object}/layout returns the layout; PUT saves it, DELETE resets it. See the
API reference. Agents use get_crm_object_layout and
update_crm_object_layout.
