How to make an inheritance relationship understandable?

In my educational game application, there are teams and the players on those teams. Historically, players could play any game they want (classic mode), but now I'm implementing a feature to limit the allowed games to the ones chosen by the team leader (teacher). We're calling this "focus" mode.

The focus can be set for the whole team, as shown, but the teacher can override per player to allow individual players to be more or less advanced than the team as a whole:

In testing, we're finding that some people don't understand this hierarchical relationship, or at least are confused by what happens when you change a team. One user thinks that if, say, you remove the "Early" level from the team focus, then it should be removed from all players, even though the whole point of the UI is to allow players to differ from their team. On the other hand, maybe that is a reasonable interpretation of the UI, and there should at least be a prompt asking if that's what you'd like to happen.

Can anyone offer guidance about how, in a situation like this, changes to a parent should propagate to its children and how such a relationship should be represented in the UI?