As an HR administrator, the platform notifies you when something happens that you should know about. The volume is deliberately low — the bell is meant to be useful, not noisy.
Where they live
The bell in the top bar shows your most recent notifications, with an unread count. The full archive is at /{slug}/app/notifications.
What you receive
Triggers in v0.5:
CANDIDATE_APPLIED— a new application has landed in one of your hiring pipelines. Includes the candidate name, the role, and the screening score.CV_SCREENED— a CV screening has completed. Most useful when you have set a low auto-advance threshold and want to see screening results land.CANDIDATE_HIRED— a hire handoff has completed. You are notified so you can verify the new employee's onboarding has been initiated.ASSESSMENT_COMPLETED— an assessment you assigned has been submitted. Useful for closing the loop on assigned work.PLAN_EDITED— a growth plan you co-edit has been updated by another party. Useful for staying in sync with line managers and employees.INVITATION_ACCEPTED— someone you invited has accepted and created their account. Useful for confirmation that a new hire is set up.
What you do not receive
- Every action by every user. The platform deliberately does not surface routine activity. Plan edits, for example, are batched (a burst of edits within ten minutes from one actor produces one notification).
- Other administrators' invitations. If a fellow HR Admin invites someone, you are not notified.
- Workspace-internal browsing. No one is notified when someone reads a profile or report.
Filtering and managing
From the full archive at /{slug}/app/notifications:
- Filter by type. Show only candidate-applications, only plan-edits, etc.
- Filter by read state. Unread only.
- Mark individual notifications as read by clicking the dot.
- Mark all read from the dropdown.
- Delete individual notifications to keep the archive scannable.
Notification batching
Plan edits and a few other high-frequency triggers are batched. If a line manager makes ten edits to a plan within ten minutes, you receive one notification summarising them, not ten. The batching window is intentionally short — long enough to absorb editing bursts, short enough that you still see edits within the day they happen.
Email and push
In v0.5, notifications are in-app only. There is no email channel and no push channel.
The largest gap many workspaces feel is on assessment deadlines — if an employee is at risk of missing an assessment deadline, an email reminder would be useful. Email channels are on the v0.6 watch list.
What if you are getting too many notifications
The most common cause is too many open hiring pipelines. Each open role generates a notification per application; a workspace with twenty open roles can produce a hundred notifications a day.
Two paths:
- Close roles you are no longer actively hiring for. Archive them or move them to draft.
- Adjust your auto-advance threshold up. If the threshold is low, every screening produces a notification. Raising it reduces the surface that notifies.
What if you are getting too few
Most workspaces do not have this problem; if you do, the cause is usually that the role you are hiring for has had no recent applications, or that the assessments you assigned have not yet been submitted. The platform does not nag — silence usually means there is nothing to do, not that something is broken.
Next
AI usage in your workspace — what touches AI, where to read transparency notes, and how the quota works — is covered next.