

Explains the cause of RM Unify Audit log error "User could not be created in CC4".
Details the requirements and behaviour of the MIS-sourced user rename functionality, which is available to RM Unify super admins.
CC4 reported the User was not created but on inspection the User is in CC4".
Explains why clicking a Google Workspace tile from the RM Unify launch pad redirects the user to the Google account picker page.
Provides steps to block/unblock users in Microsoft 365.
Describes the expected Glow user transfer behaviour within a multi-school RM Unify Network Provisioning.
Explains how to add users to additional groups in the Active Directory.
Details the steps required to link your existing Accelerated Reader or Accelerated Maths accounts to your RM Unify accounts.
... the cause of the RM Unify Audit log error "The requested Username cannot be used as there is already a managed AD user account with this name.".