At Sync, your SIS stays the source of truth and NexusPlan reads from it — so onboarding is mostly a week of invitations, not a migration. Teachers do nothing at all. Here's the whole path, role by role, in order.
Two speeds, same result: self-serve — sign up, pay by card, and your school portal exists in minutes — or white-glove, where we set everything up with you end to end. Either way you land in the setup wizard: school name, logo, and your color theme.
Enter your Veracross credentials — stored encrypted, scoped to your school, used only for your sync. Classes, rosters, schedules, assignments, and grades start flowing in on their own. (OneRoster, FACTS, Blackbaud, Google Classroom: Coming soon.)
At Sync there is no teacher step — teachers keep posting assignments and grades in the SIS exactly as they always have, and NexusPlan picks it all up. This is the point of Level 1.
Zero change management for faculty.
From People, send invite links for fellow administrators, advisors, and IT. Every link carries an expiring code and a fixed role — there's no open signup to police, and no one ends up with more access than they were given.
Advisors redeem their invite and sign in. The administrator then links each advisor to their advisees in the console — that link is what powers the triage view and per-student detail. From day one, advisors see who actually needs them.
In Settings, pick which cards students see on their home screen, set an announcement for launch week, and double-check branding — the portal should read as your school's tool before the first student ever signs in.
Student accounts come from your SIS data plus invite links with expiring codes — no self-registration. Because the sync has been running since Phase 1, the first thing a student sees is their own real assignments, already ranked.
On first sign-in, students declare their free time and recurring commitments — practice, a job, family dinner. A short guided tour walks the tabs. This one honest step is what makes every plan afterward fit real life.
The administrator sends parent invites, each parent redeems theirs, and then the administrator links parent to child in the console — a guardian link is what turns a parent account into a read-only window on that child's week. Multiple children, multiple links, one sign-in.
Linked parents see the week; nobody sees more than their own child.