Start with verified access
Select an organization and discover a granted Recruit workspace. Application permissions and the hiring-team role both apply. Read team.me. Recruiters manage hiring, hiring managers see managed roles, and interviewers see assigned interviews and candidates.
Prepare a role and public job board
Create a role, its questions and stages, then open or approve it as required. Configure the job board slug and title before publication. Only open roles appear publicly. A published job board accepts anonymous applications without editing an existing candidate with the same email.
Manage candidates and applications
Create or import candidates, inspect duplicate and per-row import outcomes, and create applications for discovered roles. Move applications using actual stage ids. Interview and scorecard access follows hiring-team visibility. Candidate erasure is irreversible and requires workspace:delete plus explicit input confirmation.
Verify communications
Templates support a constrained set of merge fields. Inspect email status and error fields; a handler response alone does not prove delivery. Notify event delivery connects organization-scoped subscriptions using the caller’s authorized user credential, not a service key.
Use the action reference
Every one of the 73 application actions has a worked guide with request fields, actual synthetic handler responses, errors, verification and recovery. Fixture identifiers and timestamps are examples; discover granted resources before executing.
Action reference
Evidence
Actual dispatcher and migration-created SQLite or Worker handlers; Auth/workspace identity, object storage, mail and Notify dependencies are simulated. These synthetic fixtures establish no live authorization or delivery.