Using Collaboration, Notifications, and Activity Feed

Start with the notification bell

1. Use the bell in the top bar as your personal queue for collaboration events that mention you.
2. Keep unread-only on when you are triaging fresh work, then switch back to the full list when you need recent context.
3. Open View from the notification item to jump back into the related record instead of trying to remember which site, inspection, or work order changed.
4. Mark individual items read when you have handled them, or mark all read when the queue has genuinely been cleared.

Use Activity Feed when you need the office view

1. Open Collaboration → Activity Feed when the question is broader than one notification.
2. Filter by resource type when you only care about sites, inspections, defects, quotes, or work orders.
3. Filter by event type when you want to isolate creation, assignment, status changes, comments, or thread changes.
4. Filter by user when you are trying to understand who changed a shared record during a busy operating period.

Use the feed to trace operational state

1. Treat the feed as the shared record of what changed across the workspace, not as a replacement for the live record itself.
2. Use the linked resource to move back into the underlying site, inspection, or work order once you know which event matters.
3. Pair the event summary with the actual desk that owns the workflow, because scheduling, inspections, and commercial desks still remain the source of truth for the live job.

Share records without breaking workspace boundaries

1. Use the page-level collaboration controls when a site, inspection, quote, schedule, or work order needs another person's attention.
2. Check presence before making a competing edit so the team can see who else is active on the same resource.
3. Use comments and mentions for internal follow-up, then open the linked record from the notification or activity item.
4. Use share links only for the intended resource and audience; they do not replace workspace role checks or customer-facing delivery controls.

Keep visibility rules realistic

1. Notification items belong to the signed-in user, so one person clearing their queue does not clear the queue for someone else.
2. The cross-resource Activity Feed is an admin-facing Collaboration desk, so use it for office triage rather than expecting it in every field account.
3. Access to the Activity Feed is enforced at the server level, not just in the UI. Org admins and owners can query it scoped to their own organisation. Engineers are not permitted to access the feed and will receive a permission error if they try directly.
4. If collaboration controls look incomplete, check role and workspace before treating it as a broken history surface.

Troubleshooting

Reference surfaces

1. Use Activity Feed for the event-stream controls, filter model, and linked-resource behavior behind this guide.
2. Use AI Assistant when collaboration includes route-aware AI help rather than human mentions and event review.
3. Use the Capability and Access Atlas when collaboration history appears for one role but not another.