Your inbox and notifications
Where everything waiting on you is listed, and how Deliverd tells you about it: in the app, by email, in Slack or Teams, and on your phone's lock screen.
Inbox is the one list of what needs you. It does not decide anything itself: every row links to the page where the thing is done, so the same rules apply wherever you act.
The three tabs
| Tab | What it lists |
|---|---|
| Needs attention | Approvals you were asked to decide; reviews and requests for information addressed to you; people asking for access to a report you own; and open reader feedback on reports you own (one page of it — the most recent 25 threads). Administrators also see approvals that named nobody, publishes held for approval, and access requests and feedback across the organisation. |
| Waiting | What you asked for that nobody has settled yet: your approvals, reviews and requests for information. |
| Completed | Approvals you were named on or decided, and everything you asked for that has been settled, expired or withdrawn — newest first. |
Each row says who asked (an agent or a person), the status, and for anything open its deadline. When a request was addressed to a team rather than to named people, the row names the team.
Asking for something yourself
Ask for at the top of the inbox starts an approval, a review or a request for information. What you ask for then appears under Waiting until someone answers.
How you are told
A request reaches you on every channel that is set up for you at once. None is the only route: if a chat message or a push notification cannot be delivered, the email still arrives.
| Channel | When you get it | What you can do from it |
|---|---|---|
| In the app | Always, while you are a member. The bell in the header lists your notifications. | Open the request. |
| Always for approvals, reviews and requests for information addressed to you. | Open the request. For most approvals the link lets you decide without signing in — see Deciding from an email. | |
| Slack | For approvals, once an administrator has connected your Slack workspace under Admin → Integrations. It arrives as a direct message. | Approve or Decline in the message, or open the request. |
| Microsoft Teams | For approvals, once the organisation's Teams app is in your own chat. | Approve or Decline in the card, or open the request. |
| Browser push | For approvals and their reminders, on each device where you turned it on in Settings. | Tap to open the request, through the same link your email carries. |
Deciding from an email
The link in an approval email is your own. It opens the request as you, without a sign-in page, and pressing Approve or Reject on that page is what decides — opening the link never does, so a mail scanner that follows it decides nothing. Everything is checked again when you press: that you are still a member, still asked, and that the request is still open.
The link lasts until the request's own deadline or for a week, whichever comes first; a reminder carries a fresh one. From a link you can approve, reject and correct details, but asking a question or bringing somebody else in needs you to sign in.
- High and critical risk requests open the sign-in page instead: the email alone is not enough for the requests that matter most.
- A request an ethics rule flagged also needs you to sign in, because approving it takes a written reason. See Concerns and reasons.
- If your organisation requires single sign-on, every link goes through your identity provider as usual.
- Restricted fields — details the requester marked sensitive — are hidden when you are not signed in.
Deciding in Slack or Teams
The buttons decide for whoever presses them. The first press links your chat account to your member account, using the address the chat platform holds for you; after that every press is recognised. The same checks run as on the page, so pressing Approve on something a colleague has just approved does nothing but show you the outcome.
- A request an ethics rule flagged shows Decline and a link, but no Approve: approving it needs a reason, which a button cannot carry.
- A button approves the request as proposed. To correct its details, open it.
- When a request needs more than one approval, your press is recorded and the card says another approver is needed.
- Once a request is decided anywhere, every chat copy of it stops offering buttons and shows how it was settled.
- Members of an organisation that requires single sign-on are not sent chat cards; they decide on the page.
Reminders and deadlines
A request may carry a deadline. When it passes with nobody having decided, the request expires: it can no longer be decided, and the agent or person who asked is told.
- Approvals: if you have not answered, you get one reminder — in the app, by email and by push — when a quarter of the time before the deadline is left. A request with no deadline has no reminder.
- Requests for information: if you have not sent your answers, you get one reminder, in the app and by email, once the answer is due within a day.
- Reviews carry a deadline but no reminder.
Standing rules your administrators set can also bring more people into an approval that has waited too long. That adds approvers; it never removes you. See Policies.