We considered it, but (in this case) the application's use-case is on shared/communual "front-line" machines (hence why we added quick-user-switching), so even though ostensibly a single, human user is logged-in, we honestly don't know who is actually using the machine, and some other user who is just borrowing a machine could easily dismiss a tour/onboarding intended for the
actual user who is logged-in.
If you think that's bad, when we overhauled some incompetently written code (from a dodgy contractor before I joined) that stored passwords using reversible-encryption (ARGH!) - which was for a "feature" that allowed tenant-admins to reveal their own users' passwords (WTFBBQ!) - and switched to using correctly hashed+salted passwords we had dozens of support calls from angry/frustrated (and yet unsophisticated...) users who said they were no-longer able to login because they never bothered to remember their password, they'd just ask their tenant-admin to tell them their own password (aiaaiaiiaiaiia) and now they couldn't do it anymore. We asked why they couldn't use the forgot-password page or a magic-link to login and they said it doesn't work because they all used fake e-mail addresses for their users (*dies*) (these tenant accounts were all set-up before things were fixed, and accounts with invalid/unverified e-mail addresses were just grandfathered-in).
We do also support OIDC (we are our own IdP, as well), so to try to make things easier for our users we'll be adding O365/AzAD soon, with sign-in-with-Google (and maybe sign-in with Facebook... excuse me while I take a cold shower) so at least some users can dispense with having a separate user-account they need to remember details for.
...so things were awful, now they're just bad, and they're getting better - but things could always be worse: Our main competitor is an on-prem VB6 app that pushes data to a "cloud" (i.e. Internet-exposed) SQL Server running off a business/residential IP address with a hardcoded SQL login userID and password shared by everyone (all of their tenants!).
------------------
...this is what the LoB software world is like. There is so much room for improvement everywhere - but all the competent uni grads join some glamorous FAANGMA company after school (well, I'm guilty of that myself...) - but I wish they'd consider un-sexy LoB software: it pays much better than FAANGMA provided you're competent and know how to negotiate. I think the LoB area gets a bad rep just because it's generally where (for want of a better phrase) less-talented people end-up which brings down the average total-comp.
I'm rambling at 3am again, ugh...