Skip to main content

How do I resolve Supervisor-related update errors?

Learn how to resolve Supervisor-related errors during bulk updates, group changes, or inactivation by choosing the correct resolution path.

Written by Lauren Baird

Answer

Use the error shown in the Admin Portal results to decide the correct next step. Supervisor-related update errors usually happen because of one of two problems:

  • the user is still classified as a Supervisor

  • the user and assigned Supervisor do not share at least one Group

Each error has a different fix, so the first step is always to identify the exact error message returned.


Steps

  1. Open ANVL Insights.

  2. Select Welcome, [Your Name].

  3. Select Admin Portal.

  4. Open User Management.

  5. Run or review the update that failed.

  6. Scroll to the results section.

  7. Find the error message in the returned row.

  8. Use the table below to choose the correct resolution path.

Error Message

When You See It

What It Means

What to Do

one_or_more_users_are_supervisors

During inactivation or bulk inactivation

One or more selected users are still classified as Supervisors

Remove Supervisor status first, then retry the action

A supervisor must be from the same group as the user

During supervisor reassignment or Group changes

The assigned Supervisor does not share at least one Group with the user

Reassign the user to a Supervisor with a shared Group, or update Group membership first

  1. If the update failed during inactivation, remove Supervisor status from the affected user, then run the update again.

  2. If the update failed during a supervisor reassignment or Group change, confirm the Supervisor shares at least one Group with the user, then retry the update.

  3. After correcting the issue, re-run the update.

  4. Review the results again to confirm the error is cleared.

Use this quick guide:

  • Inactivation failing → remove Supervisor status

  • Reassignment or Group move failing → fix Supervisor / Group alignment first

Important notes

  • These errors are usually caused by hierarchy rules, not system failure.

  • Do not keep retrying the same update without correcting the underlying issue.

  • Always review the result tables after re-running the update.


Did this answer your question?