Everyone knows about one-click registration in services, right? Like Yandex or VK. I won't throw around fancy terms, you get me. Sber recently made theirs and shoves it everywhere...

I myself enjoy this kind of authorization. Like, for the first time in my life I see some product (especially relevant while sitting on the radar) and bam, I log in, one click and I'm already inside as a client. No need for any confirmations anywhere. It's all very good.

BUT THERE IS ONE NUANCE

None of the developers (not even me) think about the fact that multiple people might need to log in from different devices using this account. They essentially have only one scenario left: password recovery.

What kind of scenario is that? I see a couple of the most obvious ones:
- if you need to let an assistant in to do something there
- if you need to let an employee in to do something there

So, I'm like a user, right? I open it, let's say I like the service. I send it to assistants, say "do something there, set it up". And I immediately forget and go do something else.

Or, for example, everything is set up, paid for, prepared, and I tell some specialized employee: "here's the service, go work in it, do this kind of work".

Got it, right?

Well, that's it, so either I initially have to dance with a tambourine and register through email confirmation, or suffer through password recovery.

Of course, you'll say now that if you're doing it for everyone, you should make a public email. But no way. I'm such a cool person that I pay for my personal service with my personal email and let everyone else touch it only temporarily. None of the aforementioned people go to this email of mine.

If you have a different opinion, write in the comments, I'll be happy to read. Or what to do in this case, what feature in the interface do you recommend adding?