Security in the ISMS is different for the Admin Portal and the Public Portal.
Admin portal security is role-based, while the public portal security is not. In a role-based security system, roles are first created and then assigned to users. Most changes to the ISMS security β including creating, editing, and assigning roles β are made from the Administration: Security feature.
Roles in the ISMS have three key attributes:
Users can have zero to many roles.
Security Level: Determines which roles a particular role is allowed to edit. For example, if Role A has a security level of 90 and Role B has a security level of 65, then users assigned Role A can edit the permissions of Role B, but not vice versa. Staff must be assigned to a security role before they can log in.
Admin vs Teacher Flag: This flag changes the data the user can access, specifically in the Office: Attendance feature.
Security roles can be assigned in both the Administration: Security feature and the Roles table in Staff: Profile: School Tab
Feature (and tab) access is controlled by a comprehensive list of ISMS features. Each feature has six checkboxes to manage access:
Note: Security can also be adjusted at the tab level within each feature for more granular control.

Version: 252 Updated: February 4, 2025
Public portal security is not role-based, and changes made will apply equally to all users. Public portal security can be set separately for parents and students, and is divided based on the track that the student is in. Additionally, public portal security depends on the school year, allowing admins to archive student data after a certain period.
Similar to the admin portal security, public portal security includes a list of features for which access can be controlled. Each feature has three checkboxes:

Version: 252 Updated: February 4, 2025