Permissions & connections / School Base Cloud
Working together needs the right boundaries.
Teachers, the school office, families and staff use the same product for different tasks. Your school decides who may view, edit or approve information.
How the steps connect
Permissions & connections
- Roles and family permissions by task
- Your school address and video services
- Versioned notices and privacy requests
Set responsibilities
Define administrative roles, teaching assignments and family permissions separately. Confidential staff records and payroll review receive their own permissions.
Connect your own services
Store a BigBlueButton API address and key per school. Credentials are encrypted. Teams, Zoom and Google Meet use your existing lesson links.
Record decisions
Version legal notices, distinguish acknowledgements from voluntary consent, track withdrawals and handle privacy requests with deadlines and progress.
Who works with it?
A family contact is not a blanket parent role. Teachers receive teaching access; staff and payroll permissions are granted separately. Approval workflows identify the responsible person and the next action.
For your implementation
The software supports your documentation. Your school is responsible for content, legal grounds and decisions. Legal advice, qualified electronic signatures and automatic deletion are not included. Meeting links do not synchronise provider accounts or calendars.
What we agree together
- Roles and approval owners, including deputies
- Approved notices, consent and privacy procedures
- Your provider access and a test using the intended roles
Common questions
Do we need a central School Base video service?
No. For now, each school uses its own connection. A conference service operated by us is not currently part of the offer.
Where do existing schools sign in?
At their own school address. If you do not have it, school login helps you find an existing school using its short name. Public demonstration schools are separate.