Roles
Who sees what.
A school system holds sensitive information such as names, classes, absences and grades. Access is therefore role-based and logged, and retention periods are defined from the start.
Connections are encrypted, accounts are kept separate and the admin area has extra protection. Which area is open to whom is documented in writing.
Security checks and maintenance are agreed separately.
The school is the controller; Globalsoft processes data on your instructions. This relationship is put in writing in a processing agreement.
For legal assessment, consult your own adviser.
By e-mail we discuss your processes, roles, existing systems and how data is moved, and set the scope in writing.
We build the solution around your workflow and connect it to e-mail, calendar, documents and payment.
We test every flow with realistic cases, train your team and go live only when it is right.
Child data is treated as sensitive, so the permission scope is kept narrow. Cantonal school and data-protection rules may differ; for the current position contact the competent county authority.
No; we do not issue legal compliance certificates. We document technical measures and the processing relationship in writing.
The hosting location is clarified with you in writing.
Roles and audit log in school software: separate permissions for management, office, teachers, parents and pupils; who changed what and when.
Learn moreHosting and backup for school software: hosting location clarified in writing, regular backups, restore tests and maintenance. Quote by e-mail.
Learn moreStudent management software for schools and courses: records, classes, parents and documents in one place. Four languages, built for Sweden.
Learn more