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 September 2, 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.
- Candidates create an account, build a profile, and apply.
- 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
A candidate has one profile for your whole organisation, reused every time they apply. A tribe only sees the applicants attached to its own postings; there is no tribe-level resume library.
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.