Recruitment Basics
What Recruitment is for
Advertising jobs on your own careers site, collecting applications, and what the organisation can do that a tribe cannot.
Last updated October 14, 2026
Recruitment gives you a careers website on your own domain, job postings to put on it, and a workspace for reviewing the people who apply.
How it fits together
- You build a Role — the reusable description of a job you hire for.
- You create a Job Posting from that role, for a tribe or for the organisation.
- The posting appears on your careers site once it is Active and within its publish dates.
- On the new careers website, candidates submit their details without an account; the former website uses a registered profile.
- You review them on the posting, move them through statuses, and email them.
Organisation and tribe
Both levels exist and both are called Recruitment, but they are not the same size.
| Organisation | Tribe | |
|---|---|---|
| Create and edit postings | Yes | Yes |
| Review and email applicants | Yes | Yes |
| Job locations, remote flag | Yes | No |
| Roles and role categories | Yes | No — uses the organisation's |
| Email templates | Yes | No — uses the organisation's |
| Careers website content and settings | Yes | No |
| Dashboard and the full Resumes list | Yes | No |
Applicants belong to the organisation
Registered candidates reuse their profile when they apply. Each new submission from the guest careers form creates a separate applicant record and does not overwrite an existing candidate with the same email address. A tribe sees the candidates who applied for its own jobs, and the resumes candidates chose to share with tribes in its area, on its Resumes screen. It does not see private resumes sent to other tribes.
It is separate from your contacts
Job applicants are not People, not CRM contacts, and not team members. They live only in Recruitment, and applying for a job does not add anybody to your marketing database.