Roles control which tasks users have access to and can also be used as a communication tool to share information with a group of users. From Core, platform managers can manage roles and add additional roles.
Personas automatically group tasks for quick access. There are two types of personas, Constituent and Application.
Pages within the “on” products correspond to tasks. To grant access to these tasks, a platform manager assigns roles.
Roles include different tasks which can be enabled or disabled.
Every user that logs into the system has the all school role by default. This is how the 'ON' products identify all users at once.
The platform manager role is considered the “super user,” although it doesn't have access to every persona and task.
For example, a user with only the platform manager role added could not offer courses in onCampus or view medical data in onRecord.
However, a platform manager can impersonate any other user in the system with any role to access most tasks. For example, he might impersonate an academic group manager to access the task for offering courses.
Note: Medical data is hidden from impersonators. Refer to Medical.
A platform manager can also grant herself these additional roles.
Constituent personas are role based, and are granted by constituent or employee roles. Access to each constituent persona is granted with these roles:
Faculty: Teacher, Non-Teaching Staff, Activity Leader, Advisor, Coach, Dorm Supervisor, Nurse, Past and Pending employee roles
Refer to Faculty Constituent Persona.
Student: Student, Incoming Student, Past Student, Candidate, Past Candidate
Refer to Student Constituent Persona.
Parent: Parent, Parent of Incoming Student, Parent of Past Student, Parent of Alumni/ae, Parent of Candidate, Parent of Past Candidate
Refer to Parent Constituent Persona.
Refer to Alum Constituent Persona.
Friend: Friend, Grandparent, Trustee, Past Trustee, clones of the Friend role
Refer to Friend Constituent Persona.
Application personas are groupings of similar application tasks.
Core: School, user, academic, and athletic data tasks.
onBoard: Admissions tasks.
onCampus: Academic, athletic, community, activity, advisory, and dorm tasks.
onMessage: Front-end website, pushpage, giving, event registration, and store tasks.
onRecord: Grading, schedule, attendance, course request, official notes, learning profile, conduct, and award tasks.
Access to each application persona is granted with these roles:
Core: Platform Manager, Data Manager, Content Editor
onBoard: Admissions Manager/Staff, Re-Enrollment Manager, Inquiry Manager
onCampus: Academic Group Manager, Athletic Group Manager, Community Group Manager, Attendance Manager, Dorm Group Manager, Activity Group Manager, Advisory Group Manager, Grade Book Manager
onMessage: Page Manager, Content Manager, Inquiry Manager, Giving Manager, Registration Manager, Pushpage2010 Manager, Store Manager, Alumni Group Manager
onRecord: Comments Manager, Schedule Manager, Attendance Manager, Online Signup Manager, Grading Manager, Award Manager, Learning Profile Manager/Staff, Conduct Manager, Nurse
Since these are task-based, users often have access to multiple application personas.
For example, academic group managers have access to onCampus because most tasks within the role are academic tasks and are grouped into onCampus. However, academic group managers also have access to Core for tasks such as Departments & Courses, Blocks, and Buildings.