If it was not granted, the answer is no.
Edova enforces more than 100 individual permissions across the platform, within each school and at the course level. Every request is checked on the server before access is granted.
Three levels of access, with individual permissions.
Each action — such as grading work, viewing the gradebook, adding users or changing settings — has its own permission.
Across the whole platform
Held only by Edova’s platform team, and every administrative action is logged.
Inside one school
Held within a single school, and never reaching into another.
On one course
Granted course by course, so helping on one class gives nothing on any other.
- Permission-level access control
- Nothing is assumed
- Checked before anything happens
- Custom roles, set up by Edova
- Per-person exceptions, made by Edova and logged
- Nobody can promote themselves
- Logged, and reflected in the menus
Six default roles, with permissions that can be customised.
This is how most schools are set up. Edova’s platform team can move a permission between roles, add one to a single person, or build a role for your school, and every change is logged.
School administrator
Runs their school: people, courses, settings, the subscription and reporting.
Teacher
Builds and runs courses, sets and marks work, and delegates to assistants.
Independent teacher
Runs their own space alone, as its administrator and its only teacher.
Assistant
Assistants receive the permissions assigned by the teacher for each course. Access can be restricted for individual assessments.
Student
Takes courses, hands in work, sees their own results.
Parent
Reads a linked child’s published results and nothing else.
Protect course materials with access controls and viewer identification.
Your material has no public web address. Videos use time-limited access, with the viewer’s name displayed on the content, and PDFs are stamped with who opened them and when.
- No shareable links
- Access expires
- The viewer’s name on videos and PDFs
- Signed in to watch
- Locked until unlocked
Your assessment material
Publishing takes a fixed copy of the questions and the rubric, so past marks keep their reasoning. Nobody can edit a rubric to change the basis of marks already given.
Every upload is checked before anyone can open it.
Scanned, verified for what it actually is, and quarantined automatically if anything looks wrong, before it reaches a single student.
- Virus-checked on arrivalEvery upload is scanned before anyone can open it.
- Suspicious files are held backAnything flagged is quarantined automatically: the file is refused, and the Edova team can see a record of every quarantined upload.
- File types verifiedEdova checks what a file actually is, so renaming something does not get it through.
- Deleted work is recoverableThere is a window in which a deletion can be undone before the space is reclaimed.
- Kept apart from other schoolsEach school’s files are recorded in its own database, checked on every request and counted against its own allowance.
Each school has its own database.
Each school’s records live in their own database. There is no shared table where a mistake could show one school another’s students.
- A separate database for each school
- Deleted items can be restored
- Database credentials encrypted (AES-256)
- Every change to a mark is recorded in the school’s own database
- Your schoolOwn database · own credentials · own file allowance
- Another schoolOwn database · own credentials · own file allowance
- A third schoolOwn database · own credentials · own file allowance
Nobody at your school ever handles a password.
New people get a link and choose their own. Guessing is slowed down, a new password can’t be your current one, and Edova can end every session a person has open.
They set their own password
New people get an email with a time-limited link, and anyone can request a reset themselves.
Guessing is slowed down
Attempts are limited per account and per network address, and each failure is recorded with its reason.
A new password must be new
Changing or resetting won’t accept your current password.
Sign out everywhere
Sessions are tied to the device. Edova can end every session a person has open in one action, and anyone can remove their own devices.
Separate audit records for administrative actions, grading and sign-ins.
What people did administratively, what happened to each paper, and who signed in, each kept apart and never edited by the product. Teachers see each paper’s marking history in their course, including every change to its marks, and Edova exports the other two for you on request.
Who did what
Every administrative action across every school, with the person and their address. Entries show real people and real things, linked so you can open them.
Academic history
Every change of stage and every change to a mark, kept separately from the administrative record: the person, the old value, the new value and the time, with the reason for an override or for changing a published mark.
Sign-in history
Successful and failed sign-ins, with the reason a failure happened.
- A permanent history
- Enough to settle a dispute
- Exported for you on request
- Every grant is recorded
- Edova support can look, not touch
- Only Edova’s platform owner can act as a user, and each session is recorded
- Writing needs a grant that expires
Send this page to your IT team, then send us their questions.
A separate database for each school, expiring access to your material, more than 100 permissions checked on the server, and three separate records the product never edits.