Onboarding, step by step

Rolling out First Six is measured in weeks, not quarters. A typical onboarding runs around six to eight weeks, most of which is your side getting content and identity ready rather than us building anything.

Who needs to be at the table

Three roles, usually:

• IT / identity, to set up single sign-on against your identity provider and arrange the student roster feed.
• A wellbeing or student-success lead, to own the content: the weekly briefings, the help routes, and the crisis configuration.
• Someone in comms, to introduce First Six to students so it lands as a welcome, not a surprise.

Procurement and privacy are involved at the start (the HECVAT review, the data processing agreement) and then step back once the controls are signed off.

The sequence

1. Connect identity. Register First Six as an application at your IdP and share the connection details. The OIDC flow page is the technical companion for your engineers.
2. Sync the roster. Your student information system pushes the cohort in, so students resolve to the right record when they sign in.
3. Seed the content. Your wellbeing lead builds out the six-week arc, often by cloning a starter structure and adapting it.
4. Test end to end. We exercise sign-in and the roster against a test identity provider before your real one is in play, so launch day holds no surprises.
5. Introduce it to students. Comms goes out, and the cohort starts its first week.

The pre-launch checklist

Before a cohort goes live, confirm:

• Single sign-on works with a real account from your IdP.
• The roster sync runs and reconciles cleanly.
• The first weeks of content are published and targeted correctly.
• Crisis routing is configured (who gets alerted, and through which channels).
• Your privacy office has signed off and students have been told.