Every meaningful action on a candidate — a stage move, an interview scheduled, an email sent, a score generated — gets logged automatically. This article covers where to find that history, what it captures, and where the coverage still has gaps.

Who can do this: Any user with access to the candidate's profile or the job application can view its activity feed. No separate permission is required beyond the access you already have to that candidate or job.

Where to find it: The Activity Feed tab (the last tab) on a candidate's global Contact page, and within the Activity Feed view of a specific job application.

What shows up in the timeline

• Stage moves, including which stage a candidate was added into (for example, "User added candidate [Name] in Application Review stage").

• Interview activity — scheduling, rescheduling, cancellations, interview end times, and scorecard submission timestamps, all visible directly in the timeline without switching tabs.

• Self-scheduling status — a dedicated "Self Schedule Link Sent" status when a link is sent for a single-interview stage, plus a log entry for each automated reminder sent to a candidate who hasn't booked yet.

• AI scoring — when a score is generated or re-run, including the change from one score to another.

• Referral credit — since a recent fix, referral entries correctly show "on behalf of" the actual referrer rather than the person who submitted the candidate.

• Approvals and offers — approver names on job/offer approvals, and offer-related status changes.

• Consent activity — candidate consent requested, granted, or withdrawn now appears in the timeline alongside interviews, emails, and stage moves (a recent addition).

• Integration activity — for example, a background-check status update (SpringVerify) or a hire being pushed to an HRIS (Darwinbox for supported accounts) both log an entry.

• Transfers between jobs — when a candidate moves from one job to another, the feed reflects the job reference so the move is traceable.

• Automated/system actions are attributed to "System" in the feed, distinguishing them from actions a person took directly.

What's not (yet) captured

• Flow/sequence step activity — opens, replies, or step progress from an outreach sequence don't currently surface in a candidate's activity feed under a job. This has been requested but is on hold.

• Re-enrichment actions — re-pulling a candidate's LinkedIn data isn't yet logged as its own activity entry.

• Full reminder content — while a reminder being sent is logged, showing the reminder's actual email content inline in the feed is on the roadmap but not yet built.

• A "candidate already in a flow" notice — some customers have asked for a flag in the feed showing a candidate is already active in a flow before adding them to another one; this doesn't exist today.

Good to know

• The feed is paginated, even for a single candidate. If you're trying to pull activity data at scale (for reporting or analytics), the activity feed itself isn't built for that — Kula's own guidance to customers building custom reports is to look at Conversational Analytics or a dedicated reporting view instead of scraping the feed.

• There's no public API for activity history yet. A request to expose this data via API is being actively scoped as of late July 2026, but it isn't available today — the activity feed is a UI-only view.

• Actions taken through a public API token currently show as "System" rather than the integration or token's name — a known, open issue as of this writing.

• Historical entries aren't always backfilled when a logging gap gets fixed. For example, when a fix went in to correctly log AI-score knockout rejections, candidates rejected before the fix still show without that activity entry unless a migration is run separately.

• Job-level and candidate-level feeds show different things. The job-level feed focuses on administrative actions (job creation, approvals, hiring team changes); candidate-specific actions taken by a hiring manager — stage moves, rejections — currently only show up in that candidate's own feed, not the job's.

• Transferred candidates keep their own activity history per job — the feed for a transferred candidate doesn't merge history across the jobs they've been on; this is the intended, current behavior.

FAQ

• Where do I see a candidate's full history of activity? On their global Contact page, under the Activity Feed tab (the last tab), or within the Activity Feed view of a specific job application.

• Why don't a hiring manager's actions on a candidate show up in the job's overall activity feed? Today, the job-level feed only captures administrative actions. Candidate-level actions by hiring managers (like stage moves or rejections) appear only in that candidate's own activity feed, not rolled up at the job level.

• Does the activity feed show engagement from an outreach sequence, like email opens or replies? Not currently — flow/sequence step activity doesn't yet surface in the candidate's activity feed under a job.

• Can I pull a candidate's activity history through the API for my own reporting? Not yet. There's no public API endpoint for activity data today; if you need activity-style data for reporting, ask about Conversational Analytics or a dedicated report instead.

• An activity in the feed shows "System" as the actor — what does that mean? It means the action was automated rather than performed directly by a person (for example, an automatic reminder or a stage automation rule). Note that actions taken via a public API token can also currently show as "System" rather than the integration's name — this is a known issue being worked on.

Need help?

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