How hard is passing an organization ID in the JWT?
How feasible is it to embed an organization ID directly into the JWT that Zitadel issues? Are there built-in mechanisms or recommended hooks to inject a custom
org_id claim at token-issuance time? What pitfalls should I watch out for (e.g. token bloat, signature issues, claim collisions)?
Use-case: Zitadel for API Authentication and authorization (user login and machine API Tokens)
Environment: Self-hosting
Version: Will use the latest stable
Stack: Using Zitadel with our API1 Reply
Take a look at Zitadel Actions. In the docs you can find examples on how to set custom claims based on the user info
ZITADEL Docs
Actions are a powerful tool to extend ZITADEL and you might wonder what use cases actions can be used for.