Custom record page
What the Screen Is For
Staff read a custom entry, take permitted lifecycle actions and inspect its changes. The generated record view presents the current property contract.
What It Shows and Lets People Do
Actions depend on granted reach and state. Publish, archive, restore and permanent delete require confirmation; restriction errors explain links preventing deletion, and history shows attributed revisions.
States and Errors
Service refusal stays in the confirmation. A stale version offers reload. Records beneath inactive categories render read-only, and unavailable records return not found.
Patterns It Must Respect
The existing record-view engine combines generated content, asynchronous confirmations, history presentation and the shared stale-version alert.