Details

A detail page is where users read the full context for one record. It can show fields, related data, object collaboration, tags, activity, history, assignments, and actions for the current record.

The exact sections depend on the record type and the user’s access. If a section or action is missing, the record type may not use it, or the current user may not have permission to see or change it.

Custom blocks

Your organization can add its own read-only blocks to a record: a section in the detail page or the preview drawer, an item among the record’s fields, or a column in a table. They look like standard sections but their content comes from your workspace’s own interface project. A custom block shows a spinner while it loads and a short message if it fails; retry it with its refresh action. If a block says Component unavailable, the workspace interface that provides it is not published yet, so the block is expected to stay empty until your administrator activates it. These blocks never change the record. A record form can contain its own custom block for input the standard fields cannot express; see Creating and editing.

Archive, restore and delete

The record menu shows the actions available to you. Archive, restore and permanent delete each open a dialog where you enter a reason. Enter 1–1000 characters, excluding surrounding spaces. Permanent delete is available only for an archived record when the server permits it.

If someone changed the record, review the refreshed information and confirm again. A network error can leave the outcome unknown: use Retry the same request when offered. Closing the dialog does not undo an operation already sent. If the record is no longer available after success, the screen clears or returns you to its parent view.

Workspace pages can use the same supported record header and dialogs. Their author chooses the surrounding layout and navigation; your permissions still apply.