The design decision to use the alias (not the full name) in tokens and UserInfo comes down to two things: stability and URL-safety.

Why alias and not name:

1. The name can change. An organization can be renamed at any time by an admin. If the full name were included in tokens, existing tokens would become inconsistent with the current organization state, and any downstream system relying on the name as an identifier would break silently.
2. The alias is stable and safe. It is unique within a realm, URL-safe (no spaces or special characters), and immutable once set — making it suitable as an identifier in JWTs and query parameters.
3. The UUID is the canonical key. The UUID is what you should use to look up organization details (including the full name) via the Admin REST API or Organization API when you need it.

To include the organization name in your tokens:
You can add a custom Organization Protocol Mapper or a script mapper that reads the organization attributes. In Keycloak 25+, the organization claims are available on the token, and you can configure additional mappers to include the name field alongside the alias.

Alternatively, if the organization name is needed in your application, the recommended pattern is to resolve it from the alias or UUID at login time via the Organization API (GET /realms/{realm}/orgs/{orgId}) and cache it on the application side.