Manage employment
Users must have an employment record to have a staff,
Tip: If you enter employment for a Future date and time, the changes will appear as "Pending" after you Save.
-
From Core, use the People finder to choose the individual you want to work with and then select the Access tab.
-
From the Access tab of the user's profile, find the Employment tile and then select Edit employment.
-
For General, you'll enter basic information about the employee's access.
-
Determine when the employment should begin: Immediately or a Future date and time.
-
Enter a Date appointed for Tenure. This doesn't affect the user's access. It only affects reports and directories. This information appears in affinity categories.
-
If you know when employment should end, enter Withdraw date and time. When employment is withdrawn, the user's roles are updated to "Past" versions, so they no longer have access to current roles.
By default, they still have access to login. For example a Past Teacher might remain involved in a community group.
If the user shouldn't login, even using their "Past" role access, select Disable user's account.
Note: To withdraw past employees from their groups, go to the Groups tab of the user's Core profile. Some groups may also need new leaders.
-
Chose whichEmployee roles to give the user. The roles available may vary based on the capabilities installed for your school.
-
Choose the School levels the employee is associated with. The school level can impact which official notes faculty can see.
-
-
On the next tab, select which academic and non-academic Departments the user belongs to.
For each select, determine whether the user is a Member or Chair.
This adds the employee to the faculty directory and affects course recommendation access.
-
On the next tab, select which Classifications the user is associated with.
This also adds user to faculty directory and but does not affect user's access to student information
-
If Athletics is installed, then you'll use the final tab to select which Sports the user is associated with. They're organized by seasons.
This adds user to school website athletic faculty directory. The user will still need the a coach or trainer security role to manage athletic teams.
-
Select Save.
Platform managers can edit employment for users. For example, you might change which the roles, departments, grade levels, or sports associated with an employee as their career grows.
-
From Core, use the People finder to choose the individual you want to work with and then select the Access tab.
-
From the Access tab of the user's profile, find the Employment tile and then select Edit employment.
-
Enter your changes.
Tip: If you enter employment changes for a Future date and time, the changes will appear as "Pending" after you Save.
-
Select Save .
See withdraw employees.
Platform managers can withdraw employees.
Withdrawing employees moves the user to the Past
Tip: If an employee still works at your school, but their job title or responsibilities have changed, update their roles instead of withdrawing them.
-
From Core, use the People finder to choose the individual you want to work with and then select the Access tab.
-
From the Access tab of the user's profile, find the Employment tile and then select Edit employment.
-
For General, you'll enter basic information about the employee's access.
If you know when employment should end, enter Withdraw date and time. When employment is withdrawn, the user's roles are updated to "Past" versions, so they no longer have access to current roles.
If the user shouldn't login, even using their "Past" role access, select Disable user's account.
By default, they still have access to login. For example a Past Teacher might remain involved in a community group.
Note: To withdraw past employees from their groups, go to the Groups tab of the user's Core profile. Some groups may also need new leaders.
-
Enter any additional changes.
-
Select Save .
See withdraw employees.
When a user has an employee/volunteer role ( and their employment is withdrawn, their user is automatically assigned a “Past” version of the role, even if their login access is disabled.
You can remove these “Past” roles. You'll most likely do this onboarding and offboarding of employees, when troubleshooting or testing, or while performing data cleanup. For example, you can correct a user's employment history or remove access that might be lingering from the past employee/volunteer roles’ tasks.
Platform managers (and other users with access to manage roles) can do this from Core, Security, Roles. Find the past role in the list and select the # of members on its row. Next, select Members and find the user in the list. Then select More (...), Remove, and confirm the change. For details, refer to security roles and tasks.
When you remove a user’s membership from a past employee/volunteer role, a record of their previous access is saved to the user’s role history.
Note: This also enables an admin to change a specific part of the employment without undoing all the employment changes.
See withdraw employees.
Tip: If an employee still works at your school, but their job title or responsibilities have changed, update their roles instead of withdrawing them.
-
Select Core.
-
Select Users.
-
Select Withdraw employees.
-
Select the users who no longer work for the school or who won't return next year.
-
Select Next.
-
For each employee, select whether they should be withdrawn Immediately or whether the change should be Effective at a later date and time.
Note: Use the Default row to select settings for all employees in the list.
-
If users should no longer login, select Remove access.
-
Select Save & exit.
See withdraw employees.
When a staff member departs your school, disable the former employee's account on your Identity Provider IdP.
This makes the email address unavailable to the former employee and the account can be completely deactivated in the future.
However, for some situations, you may not want to disable the account, but rather change the password, such as if you need the replacement staff to have ongoing access to the departed user's inbox. This is acceptable as long as the former user did not link any other organizations to the Blackbaud ID account.
Note: By default, past