Movers
When a Mover service request is filled out a ticket will be created and added to the “Starters/Leavers/Movers” queue. This queue MUST be checked every morning to prioritise the requests correctly.
User accounts MUST be updated the evening before or on their Move date. Where the date falls on a bank holiday or weekend, we MUST ensure an appropriate change date is agreed with the user and HR.
Update Details
Ensure the following details are updated correctly:
- Job Title
- Department
- Phone number – Mobile, Teams land line or both
- Full address and office name for their contracted office
- Company Name(in Azure AD) – ESP or HS
- Manager
Updated Groups
Ensure the user has the correct Core groups for their new role:
- All Teams
- All Hello Student Teams (Operations only)
- Exclaimer signatures applied
- Birmingham Hub or London Hub
- ESP - * (For Empiric assign the correct department)
- City - * (For site teams assign the correct city)
- Software – Deploy Core Applications
- Software – Mimecast SSO
- Software – Proofpoint Security Education
- Software – Reward Gateway
- Software – Workplace
Additional groups and/or SharePoint sites will be requested on the Mover form so ensure these are assigned correctly. Also, check if any licenses need to be added or removed in relation to the new role and the type of access that is needed. Always seek approval if you are unsure whether the user needs those permissions. It is never wrong to challenge access if you feel there has been an error i.e. a CSA needing access to Payroll or MSM needing access to the ESP – Property folder.
Assets
If the new user is replacing another and there are assets to reassign or if it is a new position, we MUST follow the Equipment Deployment Process.