This section covers our processing and options for Leavers. We commonly set exclusions for Pupil leavers in “final” years, but there are a few options available (subject to MIS support). It is not common for us to remove accounts entirely, and we generally advise against this.
Read more about Leavers in relation to the Cloud here
They would commonly be processed on their leaving date as set in the MIS. This can be configured to have a delay, so, if you have any questions regarding your current configuration then please contact our support team.
They will either be processed as normal leavers following your existing leaver’s settings or you may have a special process condition in place to only process certain leavers until a later date (normally 1st October). If you have any questions regarding your current configuration, then please contact our Support Team.
Read more about Leavers in relation to the Cloud here
If your MIS supports staff leavers, they would commonly be processed on their leaving date as set in the MIS. This can be configured to have a delay, so, if you have any questions regarding your current configuration then please contact our support team.
Read more about Leavers in relation to the Cloud here
Depending on your Azure AD Connect configuration, and whether we are moving your leavers to another OU in Active Directory, licenses may be stripped automatically. If you need licensing to be handled separately for leavers, please contact our support team.
Depending on your Google Cloud Directory Sync (GCDS) configuration, and whether we are moving your leavers to another OU in Active Directory, users may be suspended automatically. If a user is disabled in Active Directory, GCDS will usually suspend the account. If you do not need this to happen, there may be options we can suggest – for example, not moving the users. You can also change the GCDS settings around account suspension.