# Consent and disclosure: what your onboarding flow must show, and in what order

> Before a check runs, the provider must see a standalone disclosure that a background check will be run, then authorize it in writing. Roster hosts both screens in your brand, follows them with the live ID step, and fires check.consent_signed when the provider has signed.

By Dennis Drellishak, Owner. Last reviewed November 6, 2026.

## Disclosure first, then consent, then the check

The provider reads, then signs, then confirms their identity. Only then does the check run.

The FCRA asks for a clear disclosure, in a document of its own, that a background check may be run. The provider then authorizes it in writing; an e-signature counts. The check starts only after both.

The order: a standalone disclosure; the provider signs the authorization; the live ID step with their ID and a live selfie; then the check runs and check.consent_signed fires.

## Keep everything else off the disclosure

A disclosure crowded with other terms is the most common mistake in this flow.

The disclosure should say that a check may be run and little else. Courts have found disclosures that carried waivers or other terms didn't stand alone. Put the rest of your onboarding on its own screens.

Keep these off the disclosure: a liability waiver or release of claims, your terms of service or privacy policy, onboarding questions or the application, and marketing or messaging opt-ins.

## Some states add their own notices

Where the provider lives can add a notice or a box to ask for a copy of the report.

Some states ask for their own notice alongside the federal disclosure, or a way for the provider to ask for a copy of their report. Which ones apply depends on the provider's state, among other things. Your counsel should look at your flow once, before you go live.

## Roster hosts the screens in your brand

Your logo and colours on top, Screened by Roster underneath.

`POST /v1/checks` returns a `consent_url`, and Roster sends the provider the link. They read the disclosure, sign, then confirm their identity with their ID and a live selfie from their phone. State notices are selected for the provider's state, and the signed documents go into the record of the check.

Hosted consent for an example provider, Maya: the disclosure on its own screen, shown; the authorization signed on her phone; the state notice for her state, shown; and the live ID step with her ID and a live selfie, done.

## Your code waits for check.consent_signed

One event tells you the provider signed and confirmed their ID.

Listen for `check.consent_signed`, then show the provider that their check is under way. If they stall, `resend_consent` sends the link again. Only the provider can sign: no key, agent or teammate can consent for them.

Three things to wire up: open consent_url or let Roster send it, handle check.consent_signed, and resend with resend_consent if the provider stalls.

## You own the flow around it

We prepare the screens. You decide where they sit and why you screen.

Your team decides why you screen, when in signup the check starts, and what the provider sees before and after. If you build your own consent screens instead of using Roster's, the wording and order are yours to get right, and your counsel should review them.

## See the hosted screens in the sandbox

Run a test provider through consent and live ID this afternoon.

Sandbox keys come without a sales call. Create a check, open the `consent_url`, sign as a test provider and watch `check.consent_signed` arrive at your endpoint. [Get sandbox keys](https://www.rosterchecks.com/sandbox/) or [read the developer page](https://www.rosterchecks.com/developers/).

---

HTML version: https://www.rosterchecks.com/guides/consent-and-disclosure-in-your-onboarding-flow/
