175
SIRAS defines User Access Roles as groups of individual Rights.
Each User can be assigned many Roles but typically will only need one.
Different SELPAs may have defined additional roles intended for particular groups of users.
Most user accounts don't have an additional User Access Role.
These are what we know as 'general users'
General users will only see specific student records, user access roles added to a general user account will add more broad access.
If a staff person needs to see entire groups of student records, like at the school/site level or district level.
User access roles at the district level are not meant to be combined.
User access roles at the school or site level are not meant to be combined.
If a user is a District SPED clerk, we would not also assign them as District Admin 1.
Examples of commonly used Roles:
1. District SPED Clerk - this is the highest level of access and should only be given to users who actually need this level of access. They would be responsible for managing user accounts, manage transfers, resetting passwords, creating new accounts, assigning students, assigning schools, unlock MIS Summary page, reactivate meetings, etc.
2. District Admin 1- has the same access as a CASEMIS clerk but they are not able to create new users. This assess should be given to directors and trusted program specialists.
3. District Admin 2 - has the ability to add/remove school and providers to student records. No access to manage users.
4. School Admin 1- request and submit school transfers and add/remove school and providers to student records.
5. School Admin 2- add/remove school and providers to student records.
6. Translator - only has access to records that have the 'Translation Required' checkbox checked for a meeting and the 'Complete' checkbox not checked.
7. 504/SST Coordinator/Clerk - grants access to the 504 and SST modules, to either individually assigned students or at the district level.
How to Setup SST and 504 roles (pdf)
Siras Access Roles and Rights (Padlet link)
