Documentation · The Lagstyr handbook
What needs your attention
The first page after sign-in is headed Needs attention. It gathers, in one read, everything in your installation that is waiting for a human decision or has fallen out of its window, most urgent first. Its queues are derived from authoritative rows at the moment you load the page; they are not a separate inbox that can drift from the record.
The queues
Each queue names what is waiting and the next step that clears it.
| Queue | Next step |
|---|---|
| Pending decisions | Decide them: see Deciding a proposal. |
| Open alert episodes | Work the operations index. |
| Integrations needing attention | Contain or remediate them. |
| Unresolved external effects | Record a verdict on the effects ledger. |
| Overdue obligations | Open the commitment it belongs to. |
| Exceptions expiring or undisposed | Close or revoke the exception. |
| Paused action classes | Restore or retire the class. |
| AI system reviews due | Complete the review. |
| Workflow contract reviews due | Complete the review. |
| Impact reassessments due | Record a reassessment. |
| Tickets awaiting information | Triage them in the work queues. |
| Contract renewals due | Decide the renewal. |
| Contracts missing an owner | Name an accountable owner. |
| Contracts missing usable evidence | Attach the executed document. |
Integrations needing attention lists each installed integration with a paging condition that nothing yet answers — a blocked release, a capture that keeps refusing records, or a remediation case past its due date — and each built-in adapter whose break keeps refusing. A condition already covered by a dated remediation case or an active quarantine is not waiting on anybody and leaves the queue. Each row links to the integration or break page, where the containment and governed acts live; see Sources, structure and the operations index.
When every queue is empty the page says so plainly: Nothing on this page is waiting for a human.
Unknown is not clear
The page reads each queue separately, and a read can fail. When one does, the page does not pretend the queue is empty. It tells you how many reads did not answer and names the queues: These queues are not empty; they are unknown. Work from the next steps that did answer, and treat a missing record as missing, never as complete.
Notifications
The Notifications page lists what has been raised for you: a proposal waiting, a ticket assigned or due, an obligation overdue, an access review due, an external effect that failed or whose outcome is unknown, and governance alerts. Two actions exist, Mark read and Dismiss.
Hold on to the notice at the top of that page, because it is the most important sentence on it:
Nothing on this page approves, rejects or assigns anything. Marking read and dismissing record only that you looked; open the subject to act on it.
A notification cannot carry a decision. Neither can an email, a chat message or a calendar response. Every decision is made on the subject’s own page, inside the authenticated ceremony described in the next chapter. That is by design: it is what makes an approval in Lagstyr worth the name.