Reviewing applicants

Open a job posting and you get its applicants as cards, with filters and a slide-out panel showing each person's full profile — career history, education, skills, preferred locations, referrals, their resume and any work examples.

The four statuses

The counts beside each status always show the whole posting, not just what your current filter shows — so the numbers stay stable as you filter.

Viewed happens automatically

Opening an applicant marks them as viewed. With the unviewed only filter on, the card then disappears from the list as you close the panel — which feels like losing your place. There is a manual toggle to mark somebody unviewed again if you want to come back to them.

A rejected candidate can come back

Erasing an applicant on request

Somebody who applied for a job may ask you to remove their details, and in most countries you are required to do it. Open the applicant from Recruitment then Resumes, and use Erase Applicant at the bottom of their page. A confirmation names the applicant you are about to erase and puts the keyboard on Cancel, because there is no way back from it. Read the name before you select Erase Applicant.

It removes the applicant record, their career history, their referees, and the resume and work-example files themselves. The button is available to organisation users holding the Manage Applicants permission.

Erasure requests usually arrive as an email rather than through any screen, and often from an address you cannot immediately match to a candidate. If you cannot find the applicant, ask your Gorilla Dash contact — the same erasure can be run from an email address.

Bulk importing applicants

Use Import applicants to bring in candidates from a spreadsheet — useful when applications arrived by email or from a job board. Upload the file, match your columns to First name, Last name and Email (all required) plus phone, cover letter, skills and role, and Gorilla Dash tells you how many were created, linked, attached and skipped.

Candidates are matched on email address, so importing somebody who already applied links to their existing profile rather than duplicating it. Note that imported applicants do not receive the automatic reply — only people who apply through your careers site do.

Resumes

The organisation-level Resumes list holds every candidate who has submitted a profile, whether or not they applied for a specific job — filterable by shared status, role and date. It is where general applications land.

Shared means the candidate agreed to let their resume be seen by tribes other than the one they applied to: the tribes in the areas the candidate chose as preferred locations, or every tribe if they chose none. A Private resume is seen by the organisation and by the tribe whose job they applied for. A tribe that had already shortlisted, rejected or written notes on it keeps seeing it after it is made private.

The new careers website accepts applications without an account. A general application from this form notifies your organisation’s recruitment contact. Desired roles and preferred locations appear in the usual profile fields. Sharing a resume also notifies tribes that match the chosen state, province or region. Each new submission creates a separate application; retrying a submission keeps the same reference and does not create another record. It never replaces an existing candidate’s details just because the email address matches.

Who is emailed when somebody applies

Gorilla Dash sends one email for each new application or shared resume, and who receives it depends on what the candidate sent. A tribe here is one location, branch or business unit inside your organisation.

• A job posted by a tribe — the email goes to the team members and additional email addresses saved in the tribe’s Recruitment → Settings. Until the first save there, it keeps using Enquiry & File Upload Notification - Recipients Email Addresses. These inherited emails appear prefilled, so saving without edits preserves them as dedicated recruitment recipients. If there are no recipients, it goes to active tribe users with recruitment access, then to the organisation’s email address if no tribe users qualify.
• An organisation-wide job, or a job at a paused or deleted tribe — the email goes to your organisation's email address.
• A shared resume with preferred locations — the email goes to every tribe in the state, province or region the candidate chose as a preferred location. A candidate who only chose a whole country is not emailed to every tribe in it; their resume is still listed on the Resumes screen of those tribes.

Checking who was told about an applicant

To see who was emailed about a candidate, open Recruitment, then Resumes, and select the candidate's name, then Full Page. The Who was notified card lists each email sent to staff about them: the tribe, or Organisation when it went to your organisation's email address, the job they applied for, the addresses it went to, and when. Each entry is marked Sent, Failed or Skipped.

• Skipped means there was nobody to send it to. The entry says why: the tribe has no recruitment recipients, or your organisation has no email address. Add the missing recipients in Recruitment → Settings (for a tribe) or in your organisation's settings, and future applications will be sent.
• Failed means the email could not be sent. For an application to a job, Gorilla Dash tries again automatically, and the entry shows the time of the latest attempt. A resume shared with the tribes in the candidate's area is not sent again, so contact that tribe yourself if the entry says Failed.

The card only lists emails sent after it was added in October 2026, so an older applicant shows No staff notification has been recorded for this applicant even when somebody was emailed. Emails from the careers website, to the candidate and to your staff, are sent under your organisation's name and logo, from your own email domain when one is set up in Gorilla Dash.