Follow a candidate

Following is the per-candidate version of a subscription — a way to keep tabs on one specific process without touching your global settings. Use it when a single hire matters more than the rest: a key role, a referral you're championing, a candidate a hiring manager keeps asking about.

Following a candidate subscribes you to their activity (comments, messages, stage changes) for a specific process without going through global settings.

Follow/unfollow from the Kanban or table:

Select candidates → ⋯ → Follow candidates / Unfollow candidates.

Follow when sending a message:

In the single-candidate message composer, a subscribe toggle (notification bell icon) appears below the send button. When toggled on, you'll be subscribed automatically when you save or send the message.

What you get when following:

• Notification when a new comment is left on the candidate.
• Notification when someone @mentions you in a comment (tagged).
• Notification when the candidate replies (new message).

Good to know. The message-composer toggle is the quiet workhorse here — flip it on when you reach out and you'll hear the moment the candidate replies, without remembering to follow them separately. For more on threads, comments, and @mentions, see Communication.

Following vs subscribing. Subscribe to a job when you care about the whole pipeline; follow a candidate when you care about one person's process. They stack — following a candidate adds their activity on top of whatever your job subscriptions already send.