Skip to main content

Restoring Learner Account Info When Learners Share a Device - Genius CE & Enterprise

Overview

Genius CE and Enterprise gives learners a self-service Edit Account page where they can update their own first name, last name, email, phone, and password. This works well for learners updating their own information — but on a shared device, if one learner is still signed in and another learner opens that page and types their own name, email, and password over the top, the profile gets fully overwritten. The learner who was originally on the account can no longer sign in, and any new enrollments the second learner completes accumulate under the original learner’s account.

This article walks administrators through recovering both learners’ records using standard admin actions in Genius. No support ticket or database work is required.

Screenshot of learner Edit Account page

How to Recognize the Pattern

Look at the account’s Audit tab. The signature is distinctive, but has two parts that usually appear separately:

  • First name, last name, email, phone, and the password all change in a single self-service session, usually within a few minutes of each other. This is what a learner can do themselves from the Edit Account page.

  • The login Username is not touched by that self-service session. The Edit Account page cannot change the Username. If the account’s Username also changed, it changed through a separate administrator action — often minutes or hours later, sometimes as a well-intentioned Customer Care follow-up to make the login match the new email address. Look for it on a different row in the audit trail.

  • New enrollments start appearing under the account within a day or two of the profile changes.

The audit trail is the source of truth for the original profile values you will need to restore in Step 5. Do not skip this - the values are only easy to recover before another administrator edits the record.

Screenshot of learner Audit tab

Navigation: Administration > Users > Find User

Search for the affected account, open it, and click the Audit button. Genius opens the user’s enrollment and profile audit history.

Before You Start

Two things to gather from the Audit tab before you begin:

  • The original learner’s field values as they were the day before the overwrite. First name, last name, email, phone, and - only if the audit shows it was changed - the Username. Any field that was blank on the original record should stay blank.

  • The list of new enrollments (added after the overwrite date). These will move to the new account.

Note: If you are not sure whether an enrollment belongs to the original learner or the second learner, check the enrollment’s insert date against the overwrite date on the Audit tab. Anything added after the overwrite is almost always the second learner’s. When in doubt, confirm with the client before moving it.

Step 1: Create a New Account for the Second Learner

The learner who overwrote the account needs their own account before you can move any enrollments to it.

Navigation: Administration > Learners > Add Learner

Fill in the second learner’s real information (name, email, phone). Save.

Step 2: Re-Enroll the New Leaner into the Sections They Completed

Open the newly created learner. Enroll them in each section where completions accumulated under the original account.

From the new learner’s page, use Enroll in Section in the left menu to add each section one at a time.

Step 3: Copy the Completion Values

The new enrollments you just added will start at Active with no grade or exit date. You need to copy the completion values from the original account’s enrollments before dropping them.

Open each enrollment on the new account and update the following fields to match what shows on the original account’s Current Enrollments list:

  • Status

  • Grade

  • Start Date

  • End Date

  • Exit Date

Note: If you have several enrollments to update, use the Enrollments > Bulk Actions page. Search for the enrollments you want to change, select the rows, click Bulk edit…, fill in the fields that should change, and click Bulk Save. Status, Grade, Start Date, End Date, Exit Date, Credits, Comments, and Drop Reason can all be set from this modal. Fields left blank in the modal keep each enrollment’s existing value.

Step 4: Drop Enrollments from the Original Account

Now that the second learner has their own copies, remove the duplicates from the original account.

From the original learner’s page, open Current Enrollments. Select the enrollments that were added after the overwrite date. Click Drop selected.

Important: Dropping enrollments in a section whose status is set to Dropped Grace will automatically refund the learner. Read the on-page warning before confirming. If refunds should not happen, choose a non-Grace drop status.

Dropping is reversible. If you drop the wrong enrollment by mistake, go to the learner’s Reinstate in Section page - it lists dropped enrollments and offers to restore them.

Step 5: Restore the Original Learner's Profile

With the enrollments moved, restore the original learner’s profile fields to what the audit history showed.

Navigation: Administration > Users > Find User

Find the account and open it. Overwrite each field the second learner changed, using the values you gathered in Before You Start:

  • First Name

  • Last Name

  • Preferred Name (leave blank if the original was blank)

  • Email

  • Phone

  • Username (login) - only if the Audit tab shows the Username was actually changed. The learner-side self-service edit cannot change the Username, so on many recoveries this field never needs restoration. Check before overwriting.

Save.

Note: If a field on the original account was empty before the overwrite (for example Preferred Name, Gender, or State), leave it empty. Do not fill it in. The audit trail is the source of truth for what “before” looked like.

Step 6: Force a Password Reset on Both Accounts

Neither learner should log in with the current password. On the same Find User page for each account, check Force reset password upon login, then save

Do this on both the restored original account and the new account you created in Step 1.

The next time either learner signs in, Genius prompts them to set a new password before they can go any further.

Important: Force reset does not send an email or notification. The learner only finds out when they try to sign in. If the client wants either learner alerted sooner, contact them out of band (phone, in-person, or a separate email from the client’s administrator).

Limitations - Learning Management System Side

The recovery above splits the two learners cleanly on the Genius side. It does not re-split the associated Learning Management System user.

  • The Learning Management System still holds one user record that owns both learners’ coursework.

  • The new account you created in Step 1 gets a fresh Learning Management System user on the next enrollment sync.

  • The coursework the second learner completed while under the original account stays on the Learning Management System user that now maps back to the original learner. That coursework appears under the original learner’s restored name in the Learning Management System.

There is no way to move Learning Management System coursework between Learning Management System users from Genius. If coursework needs to be moved, it must be handled inside the Learning Management System (e.g., Brightspace, Canvas).

Troubleshooting

Issue

Possible Cause

Resolution

The Audit tab shows profile changes but no password change on the overwrite day.

The second learner may have logged in with the original learner’s password (shared credentials). Or the account uses Single Sign-On.

Continue with recovery. The absence of a password change does not change the steps — Force reset password upon login in Step 6 still applies.

I can't tell which enrollments belong to which learner.

The overwrite date is close to a legitimate re-enrollment by the original learner.

Check enrollment insert dates against the audit trail. When still ambiguous, ask the client before moving any enrollment.

Dropping an enrollment refunded the learner unexpectedly.

The section was configured with a Dropped Grace status that triggers auto-refund.

Use Reinstate in Section to restore the enrollment, then re-drop it using a non-Grace status. Reverse the refund through the standard refund process if needed.

Force reset password upon login didn't prompt the learner.

The learner logged in through Single Sign-On, which bypasses the Genius password.

For Single Sign-On tenants, coordinate the password reset through the identity provider (for example Microsoft Entra ID or Google Workspace) rather than through Genius.

I dropped an enrollment and no drop reason was recorded.

The Bulk Edit modal requires a drop Reason when the status is set to Dropped or Dropped Grace. If the status was changed some other way, no reason may have been requested.

Use Reinstate in Section to restore the enrollment, then re-drop it from the Bulk Actions modal with a Reason selected.

The Bulk Status control does not include the status I need.

Some status values are restricted to specific enrollment states.

Change status one enrollment at a time using the per-row edit, or open each enrollment individually.

Prevention

  • Encourage learners to sign out on shared devices. The overwrite scenario only happens when the previous learner’s session is still active. A signed-out learner cannot be silently overwritten by the next person on the machine.

  • Do not share credentials. Changing the password on the learner-side Edit Account page requires the current password - a real hand-off between two people usually involves sharing that current password.

  • Watch new-enrollment activity on established accounts. A learner who suddenly enrolls in unrelated coursework after a long dormant period, with a new email address on file, is often the pattern this article addresses.

Related Articles

  • Profile Merging & Duplicate Resolution - Genius CE & Enterprise. Covers the mirror case: two separate profiles for the same person that need to be combined into one. Note: that article’s statement that “the only way to reverse a merge is a database restore” applies to the automated Duplicate Users merge only, not to the profile-overwrite scenario documented here, which is fully reversible in the administrator interface.

Did this answer your question?