Background checks with your own Checkr account

If your folk work with children, the elderly, money or keys, you probably run background checks, and you probably do it with a stack of forms and a shared inbox. Causefolk connects your own Checkr account so the check is part of the application, not a separate chase.

Your account, your key

Causefolk never runs checks itself. You bring your Checkr account, choose the package and the work location, and paste your API key once. We store it encrypted, show you only its last four characters, and use it only to start checks and read results for your organization.

Who starts a check

Staff can request one from any person’s record. If you allow it, a person can start their own from their portal, or from the signup page when the cause requires a check. Either way, Checkr emails them an invitation and runs the check in its own flow; the person’s details never pass through us.

What gating looks like

Mark a cause as requiring a background check. Someone who is not cleared can see it but cannot sign up; the page tells them a check is needed and, if you allow it, offers to start one. Staff additions from the roster bypass the gate, as they do for approvals.

Cleared, and for how long

A clear result makes the person eligible for the validity period you set, a year by default. When it lapses, the gate closes again until a new check clears. A newer check that comes back needing review withdraws the standing clear until Checkr resolves it.

You decide, not the software

Causefolk never declines anyone and staff cannot mark a check as cleared. Checkr reports; you read the report in your Checkr dashboard; the gate follows Checkr’s result. The judgment stays with the humans and the provider licensed to make it.

What your folk see

Their status, the dates and a link to continue with Checkr, only when they are signed in or on the submission that created their record. Anyone else typing an email sees generic copy and a link to sign in.