A database per school
Each school's data sits in its own database, shared with no other school.
Each school's data in its own database, app sign-in with tokens unique to each school, an admin activity log and regular backups.
School data is some of the most sensitive data there is: names and phone numbers of students and parents, attendance, results, health records and payments. That is why Prima Schools is built so that every school is fully separate from the others, not a shared table with other schools.
Each school has its own database and its own file folder, subdomain and admin panel. App users sign in with a short-lived access token signed with a key unique to their school; it renews automatically and is cancelled on sign-out, and a suspended account is locked out of the apps at once, even if it is signed in. All connections to the website and the apps go over HTTPS.
Inside the school, each user sees only what their group allows, and the system refuses any action that is not allowed. The system logs the pages and actions each user opened in the admin panel with the time and IP address. Server backups are taken daily, weekly and monthly.
With its own database, file folder and domain.
For each user group and each action.
An admin activity log, and regular server backups.
No. Each school has its own database and its own file folder.
Yes. Server backups are taken daily, weekly and monthly.
It is locked out of the apps at once, even if it is signed in on the phone.
Yes. The system logs pages and actions with time and IP address; it does not keep the old and new value of each field.
Not for school accounts at the moment; sign-in is protected by passwords, permissions and session tokens.
Yes. The website, admin panel and apps connect over HTTPS.
Create your account and start a trial, or book a live demo with our team.
