Why does faculty onboarding take a week?
Because access is scattered. A new hire needs email, the learning platform, the student information system, a building badge, equipment and an approval behind each one, and every item has a different owner. Picture a professor who starts on Monday but whose Canvas account waits on IT, whose badge waits on facilities, and whose library access waits on a form nobody told them to fill in. No one holds the whole list, so the pieces arrive days apart and the first week goes to chasing logins instead of preparing a course.
What does a new faculty member need on day one?
A short, predictable checklist, ready before they arrive:
- Email and campus accounts
- The learning platform (Canvas or Moodle) with their courses
- Access to the student information system they need
- Library and research systems
- A building badge and keys
- A laptop and equipment
- The approval recorded behind each one
How does automated access provisioning work?
One flow provisions all of it at once. When HR marks a hire as starting, the flow requests each account and access, routes the approvals, and tracks everything to done, so nobody keeps the checklist in their head. The badge request, the Canvas setup and the library access all go out the same morning and run in parallel, so day one actually works. This is one of RunMyProcess's services: day-one access and secure offboarding, built around the full identity lifecycle.
The same engine also handles the changes between the first and last day. A professor who moves from one department to another, or takes on an administrative role, needs new access added and old access removed, and an automated flow makes that a single request instead of another round of chasing. Keeping access matched to a person's current role is what identity lifecycle management means in practice, and it's also what keeps old permissions from piling up unnoticed.
The flow works best when it starts from one trusted signal. When HR's system is the single place a hire, a role change or a departure is recorded, every downstream account can follow from it automatically, so onboarding and offboarding stop depending on someone remembering to send an email. The HR record becomes the switch that turns access on and off across every system.
Why does offboarding matter as much as onboarding?
Access left open when someone leaves is a security risk. An adjunct who taught one term can keep reaching the student information system for years if no one closes the accounts, and every open login is a door into student data. The same flow run in reverse closes every account and permission cleanly on the person's last day, with a record that it was done. If new faculty spend their first week chasing logins, start by writing down your day-one checklist, and we'll automate it with your team from hire to departure.
Keep reading: IT service management for higher education · AI governance in higher education
