When a user first logs in, we get their email address (in the public.user_rbac.username field). We don't seem to every check whether this is updated though, so email address changes (while keeping the same account) break the permissions checks (we look for that username in the list of people with subscription access). User's whose emails change will probably not be able to see anything in the frontend list, as their name change does propagate to the subscription_details table correctly (but not user_rbac).
Possible solution:
- Re-check the username whenever the user manually logs out and in again.
When a user first logs in, we get their email address (in the public.user_rbac.username field). We don't seem to every check whether this is updated though, so email address changes (while keeping the same account) break the permissions checks (we look for that username in the list of people with subscription access). User's whose emails change will probably not be able to see anything in the frontend list, as their name change does propagate to the subscription_details table correctly (but not user_rbac).
Possible solution: