When I get back I have to try to unsnarl an issue with user identification and access to client data where the user login is mediated by a separate app (SSO as part of a whole other project that is going on). The current requirements call for a verified identity from the admin user at account creation which puts the requirement for ID validation outside of the app my team is trying to implement. However, it has been pointed out (quite legitimately) that doing that puts up a barrier to account creation.

I'm of the opinion that we could track ID verified users downstream in the user profile in our app instead, which not only lets them get in the door nice and easy but also gives us future options about just how aggro we want to be with having an actual identifiable human associated with an account.

However, doing the legwork to validate my opinion is going to be a huge PITA. Also the vendor is onboarding next month so in addition to this nice little mess I get to revalidate pretty much all requirements against the actual capabilities of the chosen platform. Including the idea I have that we could incorporate an admin user ID verification step into profile creation. Le sigh. At least I have a minion to help.

And I don't know maybe the project director will swoop down accompanied by a beam of heavenly light and angelic choir to tell us we don't need ID validation at all....

I guess going back to work is a bit of a mixed bag.

[–] [email protected] 3 points 10 months ago (1 children)

I've seen that sort of thing done, depending on who the decision makers are there's a good chance of convincing them. In the past we've greatly reduced the strictness of automated checks because once they are in the door it's a lot easier to help them. Better that than have them struggle to get in the door and you don't know about it.

And the one I'm doing at the moment I'm pushing for no verification at all. It sounds crazy to people when we first say it, but we do backoffice checks once they start trying to pay for stuff so the account itself doesn't need those checks (we repeat the checks every order). That sounds similar to what you want, and I haven't had issues convincing anyone.

[–] [email protected] 2 points 10 months ago

Yep we can do all kinds of stuff that the account user will not notice at all (unless of course they fail a check) while having to do an ID validation is very noticeable.

[–] [email protected] 3 points 10 months ago

I understood most of that, I don't envy you!