Help Center/Admin Operations/Manage records on a CRUD engine console page
Admin Operations•Last updated: 2026-10-20•4 min read

Manage records on a CRUD engine console page

Pages whose data line ends in "(CRUD engine entity ...)" are generated from one definition of the table: the buttons you see are exactly the operations the server performs for you, nothing more.

Have questions or need step-by-step guidance on this topic?

Ask AI Copilot

Step-by-Step Procedure

1

Recognise an engine page

Under the page title the data line reads "Live: <table> (CRUD engine entity <key>)", for example "Live: i8_issues (CRUD engine entity system.issues)".

2

Read the buttons as a promise

"New Record", the pencil (edit), the bin (Archive, Remove or Delete), "Restore", the row checkboxes and the CSV/JSON buttons appear only when the engine implements that operation for this table AND your role may use it. A page without them is read-only for you.

💡 Pro Tip: Immutable data (ledgers, audit trails, event logs) never shows edit or remove buttons, not even to a super administrator.
3

Find records

Search, the status filter and the extra filter dropdowns run in the database over all records. Click a column header with an arrow to sort; click again to reverse. The pagination bar shows the true total.

4

Create and edit

The form is generated from the table definition: required fields are marked *, choices are dropdowns, links to other records are searchable pickers, JSON fields take JSON text. The server checks every value again and names any field it refuses; nothing is saved until all are valid.

💡 Pro Tip: Clicking "Save Record" twice creates one record: each opened form carries a one-time key.
5

Archive, remove or delete

The bin button says what really happens. "Archive" keeps the record and its history out of the active list (choose the archived status in the filter to see it, then "Restore"). "Remove" hides it (soft delete) and can be restored. "Delete" is permanent and is only offered for records with no history.

6

Bulk actions

Tick rows, or the header box for the whole page, and use the bulk bar. Each page states its maximum per request; every record is processed and audited on its own, and the banner lists any that were refused and why.

7

Export

Click "CSV" or "JSON" to download every record that matches the current search and filters (not only this page). Write-only fields such as secrets are never exported. The export is recorded in the audit ledger.

Expected Operational Outcome

You can create, find, edit, archive or restore records where the page allows it, and every change is recorded in the audit ledger with what changed and who changed it.

Troubleshooting & Failure Modes

Symptom: "... was changed by someone else after you loaded it. Reload ..."
Likely Cause: Another administrator saved the same record after you opened it. The engine refuses your save so their change is not silently overwritten.
Resolution: Click "Refresh", open the record again and redo your edit.
Symptom: "You do not have permission to ..."
Likely Cause: Your role may read this table but not perform that operation. Permissions come from your session; a super administrator always passes.
Resolution: Ask a super administrator, or an administrator with the role the page requires.
Symptom: "This change needs approval ... no approval policy is installed yet"
Likely Cause: The table marks this change as sensitive. Sensitive changes go through the approval policy; until one is installed they are refused and nothing is written.
Resolution: Ask the platform owner to enable the approval policy, or leave the change for a super administrator to approve.
Symptom: "... are append-only" or "... are immutable records"
Likely Cause: The data is history (comments, logs, ledgers) and by design is never edited or deleted.
Resolution: Add a new record (for example a follow-up comment) instead of changing the old one.

Was this guide helpful?

Help us refine our platform documentation