But when I say teams I mean it needs to be designed in a way that it can easily reflect a CMDB architecture, with a tree of objects, API and LDAP auth. Technical details aside, the goal is of course to integrate it with other systems.
On top of that, not all UIs are simple enough to be used by the entire organization either, but as long as it separates backend and frontend that can always be fixed.
Honestly my current plan, and this would be the 3rd time I build something like this, is to make a simplified frontend for Hashicorp Vault.
Your sarcasm isn't helpful, and serves only to falsely conflate the insecure design and horrible history of LastPass with the best-in-class 1Password. Nothing is ever 100%, but 1Password is closer than anything else I know about, including most one-off systems used by people who don't use password managers.
So it's not IF something goes wrong, it's WHEN something goes wrong. Going around thinking IF something goes wrong is delusional, even if you end up being lucky and right.