anarsultanov
commented
4 months ago Hi @codecooper,
Thank you for your suggestion!
You can customize the terminology by creating a custom theme and overriding individual messages. Alternatively, consider modifying the message bundles in the extension source code and rebuilding it.
I've been utilizing Keycloak for managing multi-tenancy in my platform, and while it has been an excellent tool, I've noticed a usability issue regarding the default terminology used for tenant management. Specifically, the term "Tenant" might not align with the language and context of all user bases.
Many platforms, including mine, use alternative terminology such as "Organization" to refer to what Keycloak terms as "Tenant." This inconsistency in language can lead to confusion among users, particularly during account creation or when selecting which "Tenant" to log into.
To enhance user experience and streamline the integration of Keycloak into various platforms, I propose the addition of an environment variable that allows developers to customize the term used for multi-tenancy. This would enable us to align Keycloak's language with the terminology utilized within our respective platforms.
I envision this feature as a simple configuration option, perhaps in the form of an environment variable like KEYCLOAK_MULTI_TENANCY_TERM, where developers can specify their preferred term (e.g., "Organization", "Workspace", etc.).
By providing this customization option, Keycloak can better accommodate diverse user bases and integrate seamlessly into a wider range of platforms. This enhancement would ultimately contribute to a more intuitive and user-friendly experience for all Keycloak users.
Thank you for considering my suggestion. I believe that implementing this feature would significantly improve the usability and flexibility of Keycloak in multi-tenant environments. I'm happy to provide further clarification or assistance as needed.