What Issues can Occur if a Staff Member has an Exception Account?
Overview
This document is for administrators who use Clever to manage their staff in myLexia
. It describes some issues you may see if a staff member has an exception account in myLexia and you are also sharing their account through Clever.
Not all exception accounts cause sync errors. Some administrator accounts and accounts for non-classroom teachers and specialists are set up purposefully as exceptions in myLexia because they are not shared with Lexia through the automated sync.
Staff exception account issues
Some staff may need exception accounts to allow them to have myLexia access. However, if a staff member has an exception account, and you share an automated account with the same name or username as the exception, it can prevent their account from syncing to myLexia.
If you see the following issues, it may be due to a staff exception account:
-
Staff can't log in through single sign-on: Staff who have exception accounts are not able to log in to myLexia using single sign-on (for example, using an application like Clever or ClassLink). Their exception account in myLexia prevents the automatically-shared account from syncing.
-
Automated classes are missing: If you manage classes through your automated sync, classes of exception staff are usually missing in myLexia. The class does not get created in myLexia, because an automated class needs to have a staff ID assigned to it.
-
Account doesn't get updated or deleted with your sync: Changes to the staff account in your Student Information System aren't reflected in myLexia. Also, if you stop sharing the account through your automated sync—for example, if the staff has left the district—their exception account won't get automatically deleted from myLexia when the account is removed from your Student Information System.
If an exception account prevents an automated account from being created, you will see one of the following errors in your logs depending on what platform you use to sync staff information:
Clever: In your user-summary log at files.myLexia.com: User with refID: frefID here] not imported. Failure reason: Username is invalid. lusername here] username already exists as an exception user.
ClassLink: In your log file, under the users.csv section: Duplicate 'Username' value. The username nusername here] is already in use by another staff member, in another district.