Hiring in Folkbase starts with a job and ends with a record. Candidates apply on your hosted careers page, move through pipeline stages, and join the directory when they accept an offer. Nothing about them is typed in twice.
Jobs and their states
A job describes one opening. Each job has a title and three fields that tell candidates and your team what kind of role it is:
- Department, so the opening sits with the part of the company it belongs to.
- Employment type: full-time, part-time, contract, or internship.
- Workplace: on-site, remote, or hybrid.
A job moves through four states. A draft stays internal while you write it. A published job is listed on the careers page and takes applications. Pausing a job puts it on hold, and closing it ends the search.
The job is also where the role declares the access it will need. Because that is settled when the job is posted, the grants a new hire should get are known before anyone has applied, and onboarding does not start with a round of questions to IT.
Your careers page
Every workspace gets a hosted careers page with an apply flow. Published jobs appear there, and candidates apply on the same page, so there is no separate applicant site to build or keep in sync with your openings.
Folkbase hosts the page for you. If you want it under your own domain, set a custom domain in workspace settings. The careers page is included on every plan, Starter included.
Pipeline stages
Each application moves through pipeline stages, so the state of a search lives in one place instead of being spread across inboxes and a spreadsheet. Moving a candidate forward changes their application, not a row in some other file.
An application keeps its history as it moves. That history does not stay behind in a separate hiring tool when the candidate is hired. It travels with them onto their record.
Jobs and the pipeline are part of the Growth and Business plans.
From offer to record
The last stage is the one the rest of Folkbase depends on. When a candidate accepts an offer, Folkbase creates their record and carries over:
- Their name.
- Their email.
- The application history.
For example, when Maya Okonkwo accepted the Product Designer offer at Northwind, record FB-2481 was created with her name, email, and application history already on it. Her team, her manager, and her start date of Jun 2, 2026 went onto the same record, and nobody copied a field from one system to another.
The candidate becomes the employee without anyone retyping who they are.
From there, the record is ready for onboarding. The access the role declared when the job was posted is waiting to be queued, and the first tasks attach to the same record. The directory shows the new hire alongside everyone else, and hiring to day one walks through the full handoff from accepted offer to first sign-in.
Because the record begins with the application, how a person was hired sits next to their access and their tasks for as long as the record exists.