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?
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?
