Aside: How can this happen? We deal with this after it happens. There may be ways in the UI but we suspect the most common ways hinge around running SQL. So SQL that is triggered and run, by time, by events that doesn't take properly into account updating all the side effects that MC needs. MC isn't reading the MGR value in the screens below from the same place that they read it when deciding what credentials you are supposed to have. Their code assumes the values are the same in both places they store them, but SQL loading doesn't necessarily abide by those rules.

The MCe API does however - a good reason to use the 'MC aware MCe API' rather than hand, or AI, written SQL to add or edit data!