Staff moving establishments between: #
When a staff member (teaching and non-teaching) transfers from one establishment to another in SEEMIS, their Glow user account moves with them allowing continuous access to stored content.
When a staff member (teaching and non-teaching) transfers from one establishment to another in a different local authority their account does not move with them. They will get a new Glow account and no longer have access to their old content, ensuring full compliance with GDPR.
Pupils moving establishments: #
In Google Tenancies
Pupils moving to an establishment across local authorities (therefore into a different Google tenancy) will have access to their previous data, for a period of 9 months, so that they can preserve access to stored content.
This allows for users to potentially return to the original local authority and access this data. It also allows for users who may have left the local authority temporarily for reasons other than moving establishments to return to school and access their stored schoolwork.
In Microsoft Tenancies
Unlike Google tenancies where users have an ‘old’ account and a ‘new’ account, Microsoft users will have one account that follows them throughout their learner journey. This is because Microsoft operates under a single tenancy, in comparison to Google’s multiple tenancies. Microsoft data will therefore remain accessible when moving between establishments and/or local authorities.
Watch the following video to find out how to manage establishment transfers. Further details are available on pages 3-7 of the Glow administrator Users Guide:
Most transfers are carried out automatically, except where SEEMIS records have not been updated. For example, if a user leaves School A to move to School B, but School A doesn’t put a leaving date in the user’s account, the account will not be able to leave School A. Alternatively, if School B does not create a new user record with a start date, the account from School A will have nowhere to go.