Extra flow for organizations

[jimaek]

If a user registers and has the ability to choose an org as his username we should show a modal about it urging him to change it first thing.
Many people dont know this functionality exists and some think we can just guess the correct value and assume the org was chosen without checking the settings.

[MartinKolarik]

We could add a modal that asks for the initial settings on account creation, but it could be quite confusing:

1. For many people, the orgs are not relevant at all.
2. The setting doesn't do anything until you adopt at least one probe and decide to add custom tags or enable the user page.

I think we should focus only on cases where it's relevant. When adding custom tags, you're already shown a list of all orgs, so this would be mostly about the public probes setting. We can update the after-adoption modal that prompts you to enable the public probes to show a list of all possible tags and allow changing it right there.

[jimaek]

That won't reach the right people.

Since giving org permissions is optional during login can we see if the user made the conscious decision to select an org?
Because that would mean he did it with the goal of setting it as his public username. And for those users we could do the moral or redirect to the right section in settings

[MartinKolarik]

Since giving org permissions is optional during login can we see if the user made the conscious decision to select an org?

I don't think so.

That won't reach the right people.

What does this mean? What flow is there where the user would not see the modal, yet the org name would matter?

[jimaek]

If he used a token to adopt the probe without seeing the adoption flow. The user who registered would be non technical and would want to prepare the account. Soon he would be the one setting the profile banner.
Then tech would ask for the token so they could setup the probes.

That's the audience I'm trying to help.

[MartinKolarik]

In such a case, the non-technical user already needs to go to the settings page to get the token and also to enable the public tags, and the org selection is right there, too. I updated the text a little to point it out.

[jimaek]

Well it's happened more than once. Nobody goes into settings and assumes the public profile is live and under the correct org name.

[MartinKolarik]

I'm not saying it doesn't happen, just that the proposed solution doesn't really solve anything:

1. If I initially select the org name, I still need to go to the settings to enable the public pages and get the adoption token.
2. Even if we show both the org selection and the public pages switch in the initial setup, I still need to go to the settings to get the adoption token.

More importantly, the whole scenario makes no sense because you're saying that:

• The user somehow knows about the existence of public pages, their exact location, and what they do, and expects them to work, without ever seeing the switch to enable them (which is the only place where we explain them).
• The user somehow knows there is an adoption token on the settings page without using the adoption wizard. But he doesn't know at all about the rest of the settings.

Basically, this can only happen to someone who already has some initial information about both of these features (pages and adoption) from you, but the information is incomplete. It seems the best solution might be just giving them more precise instructions.

Anyone else who signs up independently will discover this exactly when needed - after adopting the first probe.

[MartinKolarik]

How about this:

We show a one-time modal with both options that opens:

• After you adopt the first probe via the wizard.
• The first time you open the dash with a probe already in your account (somebody adopted it for you and you open the dash to check).

We also won't show it if the user already changed the prefix by that time. This should cover all cases but won't annoy people who don't run probes.

[jimaek]

Ok let's try that