Staff permissions

Everyone sees what their job needs.

Give each role view, add, edit and delete rights, module by module. Staff get the rights of the role they hold.

An example Teacher role: view, add, edit and delete set separately for each part of the Academics module.

The permission grid

Four rights, set separately.

View, add, edit and delete are separate switches for every part of SMS.

Grouped by module. Permissions are grouped into module cards you can expand, collapse and search.
A whole column at once. Turn one right on or off for every item in a module with a single switch.

Modules collapse to keep the grid short. One switch turns a right on for every item in a module. An example role.

Roles

Create and rename roles, then give each staff member the one that fits.

Managed by school leaders. The school owner and school admins manage roles.
Nobody edits their own role. A school admin can change staff roles, but not their own, the owner’s or the super admin’s.

An example role list, seen by a school admin: a new role is added, and the admin’s own and the owner’s roles cannot be changed.

Built-in limits

Certain roles can never be given certain areas, even by mistake.

Money stays with finance. Teachers and receptionists cannot be given access to the school’s money, such as accounting entries.
Teaching stays with teachers. Accountants cannot be given teaching areas such as marks.
Read-only where it makes sense. Some areas allow a role to view but never change. Areas a role can never hold are left out of its grid, and the page says how many.

Built-in limits for three roles. A right ticked in a barred area is still refused. Example module count.

FAQs

Roles, rights and limits.

Rights belong to roles. To give someone different rights, create a role for that job and assign it to them.

Download Academium SMS and set up your school, try a demo, or start in free mode.