# Permissions with application name

**URL:** <https://community.auth0.com/t/permissions-with-application-name/126864>\
**Category:** Get Help\
**Tags:** authentication-sessions, sessions\
**Created:** [February 8, 2024, 4:32pm UTC](https://community.auth0.com/t/permissions-with-application-name/126864 "2024-02-08T16:32:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![filipebrius](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/filipebrius/32/54658_2.png) [@filipebrius](https://community.auth0.com/u/filipebrius)\
**Post date:** [February 8, 2024, 4:32pm UTC](https://community.auth0.com/t/permissions-with-application-name/126864/1 "2024-02-08T16:32:58Z")

</div>

I have a VUE js SPA application using auth0, the implementation is pretty basic, but when I get the user information from auth0, instead of a “permissions” key, it returns a “{{some-of-my-auth0-applications-api-name}}/permissions”. I can’t find inside the auth0 dashboards how to change it.

Does anyone know how to change/fix it?

```js
Vue.use(auth0Plugin, {
  domain: process.env.VUE_APP_AUTH0_DOMAIN,
  clientId: process.env.VUE_APP_AUTH0_CLIENT_ID,
  audience: process.env.VUE_APP_AUTH0_AUDIENCE,
  onRedirectCallback: (appState: any) => {
    router.push(appState && appState.targetUrl ? appState.targetUrl : window.location.pathname);
  },
});

```

 ![CleanShot 2024-02-08 at 11.26.08](https://global.discourse-cdn.com/auth0/original/3X/2/e/2e0671c78b748e860efddcfc22d848ed3cedd87a.png)

By the way for my vue application, I’m not using the `bfp_customers_report` API/audience, but the `Msgops` one. So I can’t understand why it returns with the `bfp_customers_report/permissions` as a key inside my user’s details.

 ![CleanShot 2024-02-08 at 11.30.11](https://global.discourse-cdn.com/auth0/original/3X/0/b/0b256c133c2b31888f2f4eebdf05f2798697ae44.png)

---

<div class="post-metadata">

**Author:** ![ty.frith](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ty.frith/32/58484_2.png) [@ty.frith](https://community.auth0.com/u/ty.frith)\
**Post date:** [February 8, 2024, 5:43pm UTC](https://community.auth0.com/t/permissions-with-application-name/126864/3 "2024-02-08T17:43:37Z")

</div>

Hey there @filipebrius welcome to the community!

> [@filipebrius](#):
>
> I can’t find inside the auth0 dashboards how to change it.
> 
> Does anyone know how to change/fix it?

The permissions in the ID token with use of a namespace as pictured are added as a custom claim by a Rule or Action in your dashboard - You won’t be able to use the permissions claim directly in ID tokens as it’s a [restricted claim](https://auth0.com/docs/secure/tokens/json-web-tokens/create-custom-claims#general-restrictions). So, the way you are going about adding permissions to ID tokens currently is correct:

> [@Adding user permission to the id-token](https://community.auth0.com/t/adding-user-permission-to-the-id-token/102853):
>
> Hi I’ve got a react application and a backend project which exposes some APIs. I’ve assigned some roles to the users and some permissions to those roles. I have access to the permissions in my access token, so the backend project can authorize the user based on the permissions. But I need those permissions in the SPA too. For example the user should not be able to see the “edit post” button if he doesn’t have post:edit permission. Of course I can parse the access token payload in the SPA and …

Permissions _are_ added using the `permissions` claim in access tokens as part of RBAC:

[https://auth0.com/docs/get-started/apis/enable-role-based-access-control-for-apis](https://auth0.com/docs/get-started/apis/enable-role-based-access-control-for-apis)

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [February 26, 2024, 11:05pm UTC](https://community.auth0.com/t/permissions-with-application-name/126864/4 "2024-02-26T23:05:08Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.