My apologies for not getting back to you sooner. And yes, normally topics are automatically closed after 15 days from the last reply.
Now, after my investigation, I found that there were no issues with getting the permissions added to the access token when authenticating with Organizations.
I believe what happened involved the user only being assigned to those Permissions globally on their user profile (non-organization), instead of having them assigned as an Organization member. The difference is subtle, but it determines whether the Permissions claim is added to the access token.
If we assign the user with the read:reportsupdate:reports permissions to the user profile through the Auth0 Dashboard > User Management > Users > Roles, then when authenticating through an organization, the access token will not have these permissions. It will have these permissions if the authenticating regularly without the org_id.
If we assign the users with the read:reportsupdate:reports permissions on the Members section of the Auth0 Dashboard > Organizations > Members > Assign Roles, then when authenticating through an organization, the access token will have these permissions. It will not have these permissions if authenticating regularly without the org_id.
Thank you for the explanation! We ran into the same issue.
Like you said, the difference is subtle, and I would argue non-intuitive. I think I understand why there needs to be a difference, but I think you need to surface it in the documentation and console more clearly.
The console uses this language for roles: “List of roles this user has.” It’s reasonable to think those apply when they log in using an organization as well. Below is a screenshot from your documentation, for permissions rather than roles.