Roles & Personas
Roles control which tasks users can access. Roles can also be used as a communication tool to share information with a group of users. A user's personas are based on their enrollment and roles. Personas are also tied to past roles. For example, a user with the "Past
Platform managers can manage roles and add additional roles. To add/remove a persona from a user, edit the user's roles and/or enrollment.
Constituent personas and solution capabilities automatically group tasks for quick access.
-
Constituent Persona: Parent, Faculty, Alum, Student and Friend.
-
Capabilities (formerly "products" or "applications"): Academics, Enrollment managements, Extracurricular, School website, Core.
The persona and capability names are hard-coded into the system, and cannot be edited.
Roles and tasks
Pages, fields, and other functionalities (such as Conduct pages in Academics) correspond to tasks. To grant access to these tasks, a platform manager assigns roles (such as conduct manager and attendance manager).
Each role include different tasks. Each task can be enabled or disabled.
Every user that logs into the system has the all school role by default. This is how Blackbaud Education Management identifies all users as a collective group at once.
Platform manager role
We recommend you grant this role sparingly. We discourage cloning it.
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 or view medical data in Blackbaud Student Information System.
-
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.
Medical data is hidden from impersonators.
-
A platform manager can also grant herself these additional roles.
Constituent personas
Constituent personas are role based, and are granted by constituent or employee roles. Access to each constituent persona is granted with these roles:
-
Faculty:
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 alum, parent of candidate, parent of past candidate
Refer to Parent constituent persona.
-
Alum: alum(ni/ae)
Refer to Alum constituent persona.
-
Friend: friend, grandparent, trustee, past trustee, clones of the friend role
Refer to Friend constituent persona.
For information about roles and tasks for SKY API, see API & SDK.