Changing the displayed organization name on the login screen
Long-shot question: Is it possible to dynamically change the displayed organization name on the login screen?
Here is the real-life use case: We're a B2B2C SaaS. Our clients have multiple campaigns they run with our system. Their users (the consumers) are typically going to involve themselves with multiple campaigns, so they want to login using the credentials they already have. The problem is, the organization set up for a campaign references that campaign name directly, so I have to create a separate organization for each campaign. This isn't a problem except that when we now create a new campaign, each user needs to know they should register instead of login, because if they attempt to login they'll get the dreaded "You do not have access to this organization" message.
I could solve this if I could use just 1 organization, but dynamically change the title displayed on that register / login screen to show the name of the campaign instead of the organization. That way all users could be in 1 organization.
I make sure we send the users to the register screen instead of the login screen by default and that does help avoid the error mentioned, but inevitably, users will click the "I already have an account, login" button and then get confused by the error I just mentioned.
I know I've brought this up multiple times, but I keep finding this register vs. login flow has some friction behind it when dealing with multiple organizations that have the same user base. As mentioned previously, even a slightly better error message would go a LONG way to help the users.
Any suggestions?
10 Replies
Hey @ryno1234.,
Thanks for reaching out, and thanks for explaining your scenario is detail.
I understand the issue you are facing with multiple campaigns per organization.
I will speak to tomorrow on how to best address your scenario.
Does every organization have usually multiple campaigns? Or would they often just have 1 campaign?
@Oli - Kinde, most often our clients have a single campaign so this isn't an issue, but we've had an uptick in clients wanting to run multiple separate campaigns. As of right now, that means they're separate organizations.
Hey @ryno1234.,
Thanks for getting back to me so quickly.
My team and I are still discussing your use-case.
I will get back to you tomorrow with more information.
Hey @ryno1234.,
I make sure we send the users to the register screen instead of the login screen by default and that does help avoid the error mentioned, but inevitably, users will click the "I already have an account, login" button and then get confused by the error I just mentioned.Regarding the "I already have an account, login" button - are you referring to the "Already have an account? Sign In" link. Would it benefit you if you could remove the "Already have an account? Sign In" link on register screens?
Correct, I mean "Already have an account? Sign In".
In some ways it would benefit, but in other ways it would hinder because users who login with email / password would have to go through the account creation process every time where it is asking for their first and last name and to accept the policies. This is bad user experience IMO if they already have an account.
I just experienced this multi-organization login flow issue with a client of mine trying to sign in. His situation was multifaceted: 1) he already had a user account in Kinde, 2) He was accessing a new organization, 3) he forgot his password. Ultimately he got off the phone frustrated with the process and had brought up concerns about launching his campaign because his interaction was so poor.
Truly, I think this is SO close to being stellar! I've provided a handful of suggestions in other threads and some seem like low hanging fruit . Let me re-iterate:
* Simply improve the message which says "You don't have access to this organization", to something like "We see you have an account, but haven't logged into (Organization Name) before, click here to register for the first time)
* As an alternative to this, allow 1 org to be used and the calling app to provide a custom display name (or similar) so the org is branded differently depending upon caller.
* A more complete solution: if the organization allows self-signup and the user correctly authenticated, just add them to the organization and skip all this friction
* When a user enters the wrong password, instead of saying "Please provide a valid password", say "Your password is incorrect" (or something more direct). I had two people today not understand what that screen was saying to them because the verbiage was not clear enough. They were wondering if this meant they need to include special characters in their password to meet requirements.
Any of these suggestions, especially the first 3 would be huge.
Hey @ryno1234.,
I understand that there are many kinks in your current authentication flow with Kinde.
And it's one thing for it to be non-ideal, but its another (and much worse) for your customers to be agitated by this experience.
I know you have mentioned a lot of these issues and potential solutions in the past, and I want to assure you they have not been lost in translation or forgotten about.
I am meeting my co-founders and head of engineering team tomorrow and we will discuss your issues in detail.
Eventhough I cannot guarantee we will solve all your issues here immediately, you can be asured that at least 1 of the solutions you suggested will be implemented very soon.
Please keep the suggestions coming and keep raising the issus you come across.
We are working on getting your authentication flow to the state where it has 0 issues and no customer complaints.
I will get back to you soon with more updates on solving your issues very soon after I discuss them with my team.
Thanks @Oli - Kinde, I appreciate your time and know there's lots of feedback from customers so its hard to prioritize it all while still moving the company forward with new initiatives. Thanks for all the support.
Thanks for understanding @ryno1234.
But your issue is almost like a bug, so we need to prioritise all bugs over everything else.
Thanks for understanding though.
I will get back to you once we have clear alignment interally on how we are going to solve your issues
Hey @ryno1234.,
Back to your original question of "dynamically change the displayed organization name on the login screen"
As you know, the organization name will display on the login screen if you don't have a logo for the organization branding and your global branding doesnt have a logo either.
You can change the name of the organization either in the Kinde Admin or in the Update Organization API call.
When you change the name of the organization, this will be reflected in the login screen.
Would this solve your use-case for now?
@Oli - Kinde, no it does not unfortunately.
Most of my issues root from the fact that I have multiple organizations and users that want to access more than 1. The fact of the matter is, the user doesn't KNOW they are multiple organizations. They see a familiar login page from a brand they know and expect to use the login information they've already established.
We're forced to use multiple organizations because we want the title displayed on the login page to match that campaign that is being run by the brand / business. This necessitates different organizations.
What I was suggesting in my original question of dynamically change the displayed organization name would be to satisfy the following scenario:
* Using only a single organization for a brand so we don't encounter the "You don't have access to this organization" error
* Dynamically changing the login screen's displayed organization name based on the campaign the user is trying to interact with. In short, my suggestion was to have a single organization, but be able to brand that organization dynamically. To give you a very rudimentary and likely technically incorrect example, when users attempt to login, they might go to a URL like this: https://auth.voterfly.com/auth/cx/_:nav&m:register&psid:14f5aa75490e4b278e03380c49730277?DisplayedTitle=A%20Very%20Cool%20Campaign
I realize this isn't how we'd actually accomplish it and it begs the question if you could customize the title, shouldn't you also be able to customize the logo, and the colors, and. and. and....
Basically the overarching points is: Multiple organizations are creating issues for me both within a client that has multiple campaigns and even across client organizations as well (albeit less frequently) because some of my clients are geographically near each other so we get users interacting with these different campaigns across clients and they try to log in and get the error. This suggestion was an attempt to reduce the need for orgs.
Hey @ryno1234.,
Thanks again for elaborating on your issues again.
I think it would be best to deep dive into these issues during our call tomorrow, just to make sure I fully understand the issue at hand.