Account & billing
Users & invites
Invite teammates, see the current roster, and track outstanding invites. Up to 10 users per institution.
- Who uses this
- Every authenticated team member. Post-2026-04-24 role flatten — every member can invite.
What it is
The team roster. Lists every Org member, the date they were invited, when they last logged in, and any outstanding invites. The header shows "X of 10 users" so you always know how much headroom you have.
What you can do here
- Send an invite — by email. The invitee receives a notification telling them their workspace is ready. They sign in by going to your workspace URL, entering their email, and typing the 6-digit code we email them. There is no password to set up — sign-in is always email + one-time code, even on the first sign-in.
- See pending invites — with the date the invite was sent. Invites are good for 14 days.
- See last-login per existing member.
Common workflows
Invite a counselor
- Type their work email into the invite form.
- Click Send invite.
- They receive an email letting them know they have access to your workspace.
-
They go to your workspace URL —
{your-org}.app.celiaconnect.com— type their email on the sign-in screen, and enter the 6-digit code we email them. No password. - See How sign-in works for the full walkthrough you can forward to them.
Resend an expired invite
- Find the invite under Pending invites.
- Click Resend.
- A fresh 14-day invite goes out.
Common gotchas
Cap of 10 reached
Email [email protected] to lift the cap. Higher tiers raise the cap on Org create.
Invitee never received the email
Check spam for sender [email protected]. If still missing, resend from
this page.
The invitee says they don't have a password
Correct — there is no password, ever. Tell them to go to your workspace URL, type their work email, and watch their inbox for a 6-digit code. The code is good for 5 minutes, single-use. Same flow on every sign-in. See How sign-in works.
Why isn't there a role picker?
Customer-app is intentionally flat-roled. Every authenticated Org member sees the same surfaces. Access controls on the Slate side (where the actual student records live) handle granular permissions.