Team roles and permissions

Four roles (owner, admin, counsellor and viewer), with a named owner for every student and each workspace fully isolated.

The four roles

Roles can be changed later, so a counsellor promoted to running a team does not need a new account.

Every student carries an assigned counsellor, and the dashboard filters to that person's students. That is what enforces the rule that matters most: one named owner per student.

Invite by email and pick a role; new members default to counsellor. Team members are added on Premium at €49.99 each.

• Per-workspace isolation. One consultancy cannot see another's students.
• An immutable audit log of every consent, token refresh, email send, thread open and revocation.
• EU data residency, in Google Cloud's `europe-west1` region, with TLS 1.2 or higher in transit.

The full picture, including sub-processors, is on the security page.

The student pipeline, session types, application stages and payment methods are workspace settings, so everybody sees the same columns. Changing them is an owner or admin job.

The real test is whether someone else can take a caseload at a day's notice. Because sessions carry notes and action items, applications carry stages and deadlines, and documents sit under fixed categories, a colleague can open a student and know where things stand.

Onboarding someone into that setup is covered in education agency CRM.