guardian6 possible purposes
Guardian relationship
A parent may use this route, but parent audience language does not itself establish guardian authority.
Family authority
Support a student without inheriting the student.
Four relationship types
A role is not a bundle of every permission.
Each card states the boundary before the action. The complete purpose matrix is available on the role-comparison page.
payer5 possible purposes
Payer relationship
A payer may receive only the billing, receipt, refund, affordability and support purposes explicitly granted by the student.
sponsor4 possible purposes
Sponsor relationship
A sponsor may support a purchase and receive explicitly granted billing or receipt visibility.
support contact2 possible purposes
Support-contact relationship
A support contact may help with a support or affordability workflow when that purpose is explicitly active.
Relationship controls
Invite once. Grant narrowly. Revoke deliberately.
The raw invitation bearer is shared out of band. The website does not collect a phone number, email address or invitation token.
Invitation
Seven days by default
APP5 invitations are claim-once, expire after a bounded period and store only a token digest in the relationship ledger.
Multi-child boundary
One student relationship at a time
A relationship for one student does not infer visibility, billing authority or consent for another child.
Academic boundary
Payment does not reveal progress
Parent-safe progress belongs to OS21 guardian and consent evidence, not checkout, sponsorship or receipt visibility.
Revocation
Derived access must stop
Student-owned revocation removes relationship-derived purposes. A revoked relationship or checkout responsibility is not silently reopened.
Choose the next public guide