User instructions

Assign issues and follow alerts

Select an actual project user or department

1. Open an Issues section and select Add entry or correct an existing entry that you are permitted to edit.
2. Under Assigned to, choose Unassigned, an enabled project user, or an active department with eligible members. On the PC, choose User or Department first, then the target.
3. Review the event and save it to the hub. Saving an offline draft does not send an alert. Assignment is a separate action from checklist approval.
4. The recipient opens Assigned to me in the browser navigation, or Admin → Logs → Assigned to me…. Open an issue to read its current details and acknowledge its alert.

Browser alerts update while the application is open and connected. Department assignments notify the enabled members who can view Logs at the time of assignment. Current department members also see the outstanding issue in their assigned list. The Windows list can be refreshed explicitly. There are no email messages, operating-system notifications or background push alerts.

Marking an alert read does not resolve the issue. Resolve it by saving Issue status as Resolved, with the required correction reason. Resolved, voided and archived issues leave the active list. Reopening or changing the assignee generates a fresh alert; ordinary edits do not generate repeated alerts.

For vessel-only readers, review and link the whole book under Fleet & manifests → Vessel logbooks & permissions. That portal requires separate log rights and a hub connection; it does not use this workspace’s offline queue.

Opening and reading an alert

In the project browser and Fleet portal, an issue alert is marked read only after its authorised entry has loaded and been displayed. Only notification revisions covered by that displayed entry are acknowledged. A failed load, changed project/account or newer unseen revision must not be silently cleared.

An acknowledgement failure is shown separately: the entry may have opened even though its alert remains unread. Reading never resolves the issue. Likewise, background refresh of an already open task does not acknowledge a new task revision; explicitly opening the task can acknowledge it. Unavailable badge counts show a question mark rather than a reassuring zero.