Reference
Field reports
Issues operators have flagged on published content from the mobile app — read each report, then resolve it once you have acted or dismiss it if no change is needed.
Field reports is the inbox for problems operators find in your content. When someone in the field taps Flag an issue with this content in the mobile app, the report lands here. Open it from the sidebar under Workflow → Field reports; the sidebar shows it to people who hold Edit content or Publish.
The page is a triage list. It does not change content: you fix the item in the editor, then come back and mark the report resolved.
Where reports come from
On any published item in the app, an operator can flag an issue. They pick one reason — Out of date, Incorrect, Unclear, Safety concern or Other — and can add a note of up to 2,000 characters, then select Report issue.
- Reporting works offline. The report is stored on the device and sent when the operator is back online, so it can arrive here hours after it was made.
- A report is accepted only while the item is still published. If the item was unpublished before the report reached ROK, it is not recorded.
- When a report arrives, everyone who holds Edit content gets a notification in the bell: "An operator flagged an issue on “…”" — and, unless they have switched it off in their email preferences, an email. Selecting the notification opens this page. Only the first open report on an item rings the bell; more reports on the same item while one is still open appear here silently.
Open and All
Two buttons above the table choose what is listed:
- Open (the default) — reports nobody has resolved or dismissed yet.
- All — every report, whatever its status.
Either view shows the 200 most recent reports, newest first.
Columns
| Column | Shows |
|---|---|
| Content | The item the report is about (opens the editor), with its content type |
| Reason | The reason the operator picked. Safety concern is shown in red |
| Note | The operator's note, cut to two lines, or — if they left none |
| Reported by | The operator's display name, or their email if they have none |
| When | How long ago the report reached ROK (for example "3h ago") |
| Status | open, resolved or dismissed |
| Action | Resolve and Dismiss, on open reports only. Shown only to people who hold Edit content |
Resolve or dismiss
Read the report, open the item from the Content column, and decide:
- Resolve — you have acted on it: corrected the content, or confirmed a correction is in hand.
- Dismiss — no change is needed: the content is right, or the report is not actionable.
Either button acts immediately, with no confirmation. The report records who closed it and when, drops out of the Open view, and stays visible under All with its new status. There is no button to reopen a closed report.
What resolving or dismissing does not do:
- It does not change the content. Operators keep exactly the version they flagged until the item itself is changed.
- It does not tell the operator. The app only ever confirms that their report was delivered — "Issue reported — your content team has been notified." It never shows them what you decided. If the outcome matters to them, tell them directly.
When the page is empty or fails
- Loading… shows while reports load.
- No open reports — operators haven’t flagged any issues. appears in the Open view when nothing is waiting; No reports yet. appears under All when your agency has never received one.
- If the reports cannot be loaded, the error message appears in place of the table.
Live updates
Operators raise reports continuously and several people often triage the same list, so the page refreshes itself when a report arrives or someone else resolves one. This depends on Live updates being switched on in Settings → Features (opens the admin console). With it off, reload the page to see new reports.
The dashboard's Field reports widget summarises the same open reports by reason, with the age of the oldest — see the dashboard reference.
See also
- ReferenceThe content editorEvery card, field and button on an item's edit page — save, submit for review, publish, schedule, unpublish, restore — who can use each, and what operators receive.
- ReferenceReview duePublished content that has gone past its re-validation interval — see how overdue each item is and mark items reviewed once they have been re-checked, one at a time or in bulk.
- ReferenceDashboardEvery widget on the dashboard, what it counts, why it might not be there, and which page owns the work behind it.
- How it worksHow offline reading worksHow the operator app works with no mobile signal — why reading never waits for the network, and what a sync does when one is available.