Kula sends notifications for dozens of different events — a scorecard needs filling, a job needs approving, an export is ready — and each one can go out over email, Slack, and/or in-app, depending on your settings. This article is a full inventory: what triggers each notification, which channels it can use, and where to go for more detail on that specific one. For how to turn channels on or off, see "Configuring alert notifications."

Candidates and pipeline

• Scorecard submitted — sent when an interviewer submits their feedback. Action: Review scorecard.

• Scorecard reminder — sent to an interviewer with a pending scorecard. Repeats roughly every 24 hours by default (see Good to know on reminder cadence).

• Review request reminder — reminds an assigned reviewer of a pending application review.

• Assessment submitted — sent when a candidate completes an assessment.

• Assessment scorecard submitted — sent when a reviewer scores a submitted assessment.

• Candidate reply received — when a candidate replies to an email (via a connected Gmail/Outlook mailbox), Kula logs it to the candidate's timeline and sends an in-app notification.

• Candidate data export ready — sent when a bulk candidate CSV export finishes. The download link expires after 7 days.

• CSV import summary — sent after a bulk candidate import, with counts of files imported, skipped, and failed.

Jobs, requisitions, and approvals

• Job approval request — sent to a reviewer when a job needs their approval. Actions: Approve, Reject.

• Job approved — sent when a job clears all its approval steps.

• Job approval reminder — repeats to a reviewer who hasn't acted yet.

• Requisition approval request and reminder — same pattern as job approvals, for requisitions.

• Reminder sent by a recruiter — when a recruiter manually nudges an approver, the notification names the recruiter who sent it and excludes the job/requisition owner from the copy, so the owner isn't pinged for a reminder that isn't theirs to act on.

Interviews and scheduling

• Interview scheduled or updated — sent when an interview involving you is booked or changed.

• Interview RSVP request — asks you to confirm attendance. Actions: Yes, No, Maybe.

• Interview RSVP reminder — repeats if you haven't responded.

• Interview reminder — sent shortly before an interview starts.

• Mailbox disconnected — an in-product banner plus an email notification when your connected mailbox needs reauthentication, so scheduled sends don't silently fail.

• Zoom reconnect notification — sent when your Zoom integration token needs reauthorizing, mirroring how Kula already handles Slack token expiry.

• Flow send disconnected — if a Flow's sending mailbox disconnects mid-sequence, check for a disconnection notification before assuming the Flow itself is broken.

• AI Notetaker recording disclosure — not a notification to a Kula user, but worth knowing about: when the Notetaker joins a call, it posts a chat message ("This meeting is being recorded and transcribed for note-taking") on Google Meet and Microsoft Teams, plus a short spoken announcement when recording actually starts. On Zoom, only the chat message is added, since Zoom already gives its own recording announcement.

Offers

• Offer approval request and reminder — sent to a reviewer when an offer needs approval. The offer's full field details are shown directly in the notification, with Approve/Reject actions available from it.

• Offer accepted / declined — sent when a candidate responds to an offer.

• E-signature status updates — DocuSign/PandaDoc/AdobeSign notify Kula (and, depending on your settings, you) when a document is viewed, signed, voided, or declined. See your e-signature integration's own article for exact behavior per provider.

Sourcing, Flows, and referrals

• Referral submitted — sent when a candidate is referred to a job. Bundled under one "Referral Progress Update" setting that also covers interview scheduling, offer, and hiring updates for that referral — see Good to know.

• Project invitation — sent when someone shares a Project or sends candidates for review; everyone added gets an invitation notification.

• Project review notification — Kula users get an in-app notification when candidates are shared with them for review in a Project.

Surveys

• Survey reminder — sent to a recipient (candidate or hiring manager) who hasn't completed a pending survey.

• Survey completed — sent when a survey response comes in.

What doesn't send a notification today

• Background check reports. Kula doesn't notify you when a background check finishes — check the background check card on the candidate's job stage, or their activity feed, instead.

• A single global alert when someone is referred. Only the referring employee is notified today; there's no built-in way for Admins or HR to get an organization-wide notification when a referral comes in.

Good to know

• The Notification Centre controls which channels a notification uses, not how many you get. You can turn email, Slack, or in-app off individually per notification type, but there's no way yet to reduce the number of reminders sent for a given item — that's a separate, not-yet-shipped improvement.

• Job Approval Requests and Scorecard Fill Reminders always require at least one active channel. Kula won't let you disable every channel for these two notification types, so a critical action can't go completely unnoticed.

• Reminder cadence for approvals is roughly one every 24 hours, three times, then it stops — there's no daily-forever loop. Manual reminders (a recruiter nudging a reviewer directly) aren't limited by this schedule.

• Referral notifications are bundled, not granular. Turning off "Referral Progress Update" turns off every stage update for that referral — interview scheduling, offer, and hiring — you can't keep some and drop others. There's also no admin-level way to disable this for the whole org at once.

• Confidential jobs don't change referral notification behavior. A referring employee gets the same progress notifications whether or not the job they referred someone to is confidential — this has caused real information leaks (an employee inferring a colleague was being let go from an unrelated referral notification), so keep it in mind before enabling referrals on a confidential job.

FAQ

• How do I turn off email notifications and just use Slack? Go to Settings → Notification Centre and disable the Email channel for whichever notification types you want — most notification types can have any combination of channels turned off, except Job Approval Requests and Scorecard Fill Reminders, which always require at least one channel active.

• Will I get a reminder every day until I approve a job or offer? No — automated reminders send roughly once every 24 hours for three cycles, then stop. They don't restart on their own after that; a recruiter can still send you a manual reminder at any time.

• Can I stop getting notified every time my referral moves forward? You can turn off "Referral Progress Update" under Notification Centre → Applications & Pipeline → Referrals, but this disables all stage updates for your referrals at once — there's no way to keep, say, only the "hired" notification.

• Why didn't I get notified when a background check came back? Kula doesn't send a notification for this today — check the background check card on the candidate's job stage, or their activity feed, for the result.

• Do candidates know when an interview is being recorded? Yes — the AI Notetaker posts a chat message when it joins (Google Meet, Microsoft Teams, and Zoom) and, on Google Meet and Teams, also plays a short spoken announcement once recording starts.

Need help?

If you have questions or need assistance, reach out to us at support@kula.ai or use the in-app chat.