Create Accountor Login
Docs

Details Layout

Part of the MountDev Ops Workspace documentation. Updated November 17, 2026

MountDev Ops Workspace documentation | Updated November 17, 2026

Details Layout is what a record page's Details panel shows: which facts, in what order, and which fold under More Details. An owner or admin chooses it for the page's default, and a page can override it for one place (Helpdesk, one department).

Our Commitment

MountDev Ops is built security first. Your business data belongs to you, and you can export all of it at any time. We never use analytics or tracking of any kind inside MountDev Ops.

Every update passes all 8,865 automated checks before it ships, and every screen change is walked through before release.

What a Layout Holds

A layout is an ordered list. Each item is in the top part of the panel or folded under More Details, and each is one of:

  • A field of the page itself, such as a ticket's status or its requester.
  • A linked fact from another record the page links to, such as the ticket's company name or a project's status. It is read only and read from the source every time the page opens, so it is always current. Nothing is copied between apps.
  • A block you place where you want it: Files, Team Chat, Company, Pairing Codes, or Installs. Pairing Codes and Installs are not built into any page. A page whose records have used them in your workspace starts with that block placed, so nothing you used goes missing.

A layout can hold up to 60 items, and each fact or block can be on it once.

Who Sees What

A linked fact shows only to a person who may open that other record and see that field. For anyone else it is left out, with no empty line and no hint that it exists. The same is true of a field of the page itself that a person's role hides. The editor lists only the facts you may see yourself.

Choosing a Layout

Owners and admins choose layouts (action core.details_layout.save), for the page's default or for one place. A place with no layout of its own follows the default, and Reset (action core.details_layout.reset) makes it follow the default again. Until a layout is saved, a page starts with its fields in their usual order, the first six at the top and the rest under More Details, then Files and Team Chat.

Every save is written in the Activity Log with who saved it, which page and place, and how many items. AI agents and API keys can read a layout (action core.details_layout.get) but never change one, because a layout decides which other apps' facts show on a page.

Which Pages Have a Details Panel

A page has a Details panel when its app says so. The panel for a Helpdesk ticket is the first; the screens that draw it from a layout are described in the Helpdesk docs.

Ask Us Anything

We’d love to hear from you!