The most likely reason your AccessToken isn’t a parseable JWT is that the audience parameter was not included in your application’s login request. When the audience is missing, Auth0 issues an opaque token which is not a JWT and is only meant for fetching the user’s profile from the /userinfo endpoint.
To resolve this, you need to add the audience parameter to your login request in your application’s code. You can find the audience parameter inside Applications > APIs in your Dashboard by checking the Identifier field. This is your audience value.
Once you add the correct audience, Auth0 will issue a signed JWT as the Access Token, which will be parseable and will contain the permissions you’ve configured.
If you have any other questions, feel free to reach out!