Notifications
Every member of your workspace has a bell in the top bar of the admin app and the employee portal. It lists the updates addressed to them — a leave request waiting for their approval, a claim approved, a payslip to acknowledge, an interview they are on the panel for — with a count of the unread ones. Clicking a notification opens the page it is about.
Where notifications come from
Notifications are produced from the app's work emails. Whenever the app sends a templated email to someone who has a login in your workspace, it also writes a notification for that person:
- the title is the email's subject, rendered from the same template — your workspace's customised wording on Email Templates if you have changed it;
- the line underneath is the first sentence of the email;
- both are in the recipient's email language (their own preference, else the workspace default — see Languages & localization);
- clicking it opens the matching page — for example, a leave approval opens
My Leaves (
/portal/leaves), a new leave request opens Pending Approvals (/admin/leave/pending), and a payslip acknowledgement request opens that slip on My Salary.
Recipients are matched to members by email address: their sign-in email, or the work or personal email on their employee record. Anyone the email reaches who has no login in this workspace — a candidate, a field-visit client — receives the email only.
What never reaches the bell
| Kind of email | Why |
|---|---|
| Sign-in and account security — password reset, password changed, two-factor changes, account set-up and invitation links | They carry one-time links or report on the account itself; the inbox is the right place for them. |
| Your workspace's subscription — trial ending, renewal, payment problems, data retention | They are about the workspace's account, not about work in it. |
| Candidate emails — application received, interview invitations and reminders to the candidate, offers, rejections | Candidates have no login. Your interview panel and hiring managers do get notifications for their side of the process. |
| Field-visit feedback requests | They go to your clients. |
| Send test email from the template editor | It uses sample data, so it is not a real event. |
Choosing what appears: Settings → Notifications
Open Settings → Notifications (/admin/settings/notifications). You need
the Workspace settings permission. The page lists ten categories, each
with a switch:
| Category | Covers |
|---|---|
| Leave | Leave applications, approvals, rejections and cancellations |
| Attendance | Attendance corrections, overtime requests and missed clock-in or clock-out reminders |
| Pay | Salary processed, payslip acknowledgements, bonuses, salary changes and loans |
| Expenses | Expense claims submitted, approved or rejected |
| Documents & letters | Document reviews, HR letters, profile change requests and address verification |
| Performance | Tasks, daily and sales reports, and appraisals |
| Assets | Assets issued, returned or overdue, and the handover summary |
| Joining & leaving | Onboarding, probation, confirmation, transfers, promotions and separations |
| Hiring | Interview invitations and reminders for panel members, and offer responses for hiring managers |
| Company news | Published announcements and birthday wishes |
Every category is on until you switch it off. A change is saved as soon as you flip the switch, applies to everyone in the workspace, and affects only notifications created from then on — ones already delivered stay in people's bells.
Bell switches and email switches are separate
Whether each email is sent is still set message by message on Settings → Email Templates. The two settings do not affect each other:
| Email Templates (that message) | Notifications (its category) | Result |
|---|---|---|
| On | On | Email and notification |
| Off | On | Notification only |
| On | Off | Email only |
| Off | Off | Neither |
So you can, for example, stop the missed-clock-out reminder email and keep the reminder in the bell.
One workspace-level condition stops both channels: a workspace that has become read-only (its subscription lapsed) sends neither operational emails nor notifications.
Reading, clearing and keeping
- The count on the bell is refreshed every minute and whenever the browser tab regains focus.
- Opening a notification marks it read; Mark all as read clears the count.
- View all notifications opens the full list, with All and Unread
tabs — at
/admin/notificationsin the admin app and/portal/notificationsin the portal. - Read notifications are deleted automatically 90 days after they were created; unread ones after 180 days.
- Each workspace has its own notifications. Someone who belongs to two workspaces sees each one's notifications only while signed in to it.
When you sign in as someone else
When an administrator uses Sign in as user (see Access control), the bell shows that person's notifications, but opening them does not mark them read and Mark all as read is not offered — the unread state stays the person's own.