When multiple views could apply to the same person, Recruiterflow resolves them in a fixed order, every time:
Personal > Specific-user > Team > All users
The most specific view to that individual always wins.
Worked example: Priya is on the Exec Search team, which has a Team view. An admin has also set up a Specific-user view just for Priya. And Priya has built her own Personal view. All three exist at once — but Priya sees her Personal view that she has set for herself.
If Priya deletes her Personal view, she'd drop down to the Specific-user view built for her. If that didn't exist either, she'd see her Team view. Only with none of those does she fall back to Standard.
Things to know:
This priority is fixed — it can't be reconfigured per account.
Publishing a Team or Specific-user view does not automatically override an existing Personal view, unless the publisher checks "Override personal views."
This is the first thing to check when a user says "I'm not seeing the layout I expected."