Your app already gets a token signed by ngris with every request from a signed-in user: who they are, their email, their roles. Now it can also carry the values you keep on each user, such as their tenant, plan or employee ID, so your app trusts them the same way.
What's new
- In the signed token, under Sign-in & access › Your app › User metadata: add the metadata keys the token should carry. In the API it is
token_fieldsin the endpoint'sforwarding_config, and the MCP server's registration policy tools take it too. - A
customclaim. The token carries those keys with the values you set on the user, for example"custom": {"tenant": "acme", "seats": 12}. A user without any of the keys gets nocustomclaim, so treat a missing key as unknown and refuse rather than fall back to a default. - Whole values, never cut. Up to 20 keys and 1 KB in all. A key that doesn't fit is left out whole, so your app never reads half a value.
- See it before you save. The decoded token on the same page shows each user's
customclaim as your app will receive it.
Get started
- Set metadata on your users (dashboard, API, CLI or MCP).
- Open the endpoint's Sign-in & access › Your app and add keys under In the signed token. Save.
- In your app, read
customfrom the token you already verify. - Read the docs: The signed token.