Application Board (Kanban)

Recruitment applicants are tracked per job posting under Job Applications. Each application sits in a pipeline stage, and the stage is what moves a candidate forward from a first application through to a hire, rejection, withdrawal or hold. This article covers where applications live, what the default pipeline stages are, and how stage changes relate to the rest of the Recruit module.

There is no separate "Application Board" item in the Recruit navigation — applications and their stages are managed from the Job Applications screen.

Who can use it

Users whose role grants access to the Recruit module's Job Applications screen. If Job Applications does not appear in your navigation, ask a Company Admin to grant the recruitment permission for your role.

Prerequisites

• At least one job created under Recruit → Jobs (/account/jobs), with a status of Open.
• At least one application recorded against that job — either submitted through the public Career Page or added from the Recruit module.

How to Access

Recruit → Job Applications — /account/job-applications

Related recruitment screens:

Pipeline stages

PMSuite ships with these default recruitment pipeline stages, in order:

1. applied
2. screening
3. phone_screen
4. interview_round_1
5. interview_round_2
6. assessment
7. offer

Terminal outcomes: hired, rejected, withdrawn, on_hold.

Working through the pipeline

1. Open Job Applications and locate the applicant you want to progress.
2. Open the application to review the candidate's submitted details.
3. Move the application to the next stage that matches where the candidate actually is (for example, from screening to phone_screen once a call is arranged).
4. Schedule any interview from Interview Schedule (/account/interview-schedule).
5. When you are ready to make an offer, raise it from Offer Letters (/account/job-offer-letter), where each offer carries a status (Accept / Pending), an expiry date and a joining date.
6. Close the application on a terminal stage — hired, rejected, withdrawn or on_hold.

When an applicant submits an application, the confirmation email sent to the candidate names the position they applied for, so candidates who applied to several of your postings can tell the messages apart.

Effect on Other Features

• Jobs: Applications are tied to the job posting they were submitted against; a job's status (Open / Closed) controls whether it is still collecting applications through the Career Page.
• Interview Schedule: Interviews are scheduled and managed as their own records under Recruit → Interview Schedule.
• Offer Letters: Offers are tracked separately with their own status, expiry date and joining date.
• Candidate Database: Candidate records persist in /account/candidate-database and can be reused across job postings, so a candidate you did not hire this time is still available for a future opening.
• Reports: Recruitment-specific reporting is available at /account/recruit-job-report.
• Google Calendar: If the Google Calendar integration is active and verified for your company, PMSuite pushes matching records out to the connected Google Calendar. The sync is one-way — PMSuite → Google. Items created directly in Google Calendar do not appear in PMSuite; create them in PMSuite instead.
• Slack: If the Slack incoming-webhook integration is enabled under Settings → Notification Settings → Slack, selected PMSuite events are posted into your Slack channel (one-way, PMSuite → Slack).

Limitations

• No dedicated board route. There is no separate Application Board page in the Recruit navigation. Workaround: manage stages from Job Applications (/account/job-applications); use the Recruitment Dashboard (/account/recruit-dashboard) and Reports (/account/recruit-job-report) for an overview of pipeline volume.
• Stage names are pipeline keys. The default stages use system keys such as phone_screen and interview_round_1. Workaround: agree internally on what each stage means so everyone reviewing the pipeline reads it the same way.
• Google Calendar is one-way. Recruitment-related calendar items created in Google do not flow back into PMSuite. Workaround: always create the record in PMSuite and let it push out.

Troubleshooting

Job Applications is not in my navigation. Your role does not have the recruitment permission. Ask a Company Admin to grant access to the Recruit module for your role.

A job is not receiving applications. Check the job's status under Recruit → Jobs (/account/jobs). Only jobs with a status of Open collect applications; a Closed job stops accepting them.

A candidate does not appear under a job. Check the Candidate Database (/account/candidate-database) — candidate records are stored there independently of any single posting, so a candidate can exist without an application against the job you are viewing.

Applicants say the confirmation email is unclear. The candidate confirmation email includes the position applied for. If a candidate reports otherwise, confirm which job the application was recorded against on the Job Applications screen.

Related Articles

• Job Applications
• Creating Jobs
• Interview Scheduling
• Offer Letters
• Recruitment Dashboard
• Recruitment Reports