Admin Reference
Activity Feed Route Reference
Understand the unified event stream, filters, resource links, and why Activity Feed is history context rather than the source of truth.
Before you start
- You need cross-resource change history rather than one route’s live edit controls.
Expected outcome
You can use Activity Feed as a triage and audit-style context surface without confusing it for the underlying record.
What this route is for
Activity Feed is the cross-resource history desk for admins who need to know what changed, who changed it, and which record now owns the next step.
Visibility and capability notes
| Item | Details |
|---|---|
| Route id | activity-feed |
| Visibility | Customer-facing admin route. |
| Capability notes | This route is history-first and does not replace the underlying owning desks. |
| Direct inbound | Shell nav, collaboration workflows, and history-oriented review activity. |
Main regions and controls
| Surface | What it does |
|---|---|
| Activity table | Time-ordered cross-resource event stream. |
| Filter controls | Resource type, event type, actor, and pagination. |
| Resource links | Open the owning record when a resourceHref is available. |
Key actions
- Filter by resource type, event type, or actor.
- Page through the event stream.
- Open the linked record from the
Resourcecolumn.
Filters and URL state
- Resource types include
site,system,asset,inspection,defect,quote, andwork_order. - Event types include
field_updated,status_changed,comment_added,mention_triggered,thread_resolved,thread_reopened,created,deleted,assigned, andunassigned. - Filter state is local React state rather than a dedicated hash-state adapter.
Outputs and side effects
- The route itself is read-only.
- Its main side effect is navigation back into the owning resource desk.
- It helps explain change history, but it does not edit the resource.
Inbound links
- Shell
Activity Feednavigation. - Collaboration and history review workflows.
Outbound links
- Dynamic resource links into
sites,systems,assets,inspections,defects,quotes, andwork-orders
Indirect handoffs
- Activity Feed is often the fastest bridge between "something changed" and "which desk owns the fix."
- It is especially useful when the office needs cross-route context without knowing whether the issue belongs to Sites, Scheduling, Inspections, or a commercial desk yet.
Troubleshooting
| Symptom | What to check |
|---|---|
| The stream looks empty | Re-check the local filters for resource type, event type, actor, and page state. |
| A resource link is missing | Not every history row has a usable resourceHref, so open the owning desk manually if needed. |
| The feed explains a change but not the current record state | That is expected. Open the owning route to see the live record. |