Eh, I have a hard time even granting this one exception. The problem is turnover—a single password is fine when it's an individual who purchased the software. A

Eh, I have a hard time even granting this one exception. The problem is turnover—a single password is fine when it's an individual who purchased the software. As soon as it's a company a shared password becomes untenable because people who are not intrinsically part of the company will need to know the password, and those people can and do leave. The only safe way to handle this is to reset your password every time someone leaves, and that's not scalable for any business with more than a dozen people and a dozen vendors. In your example, what path forward makes sense would depend on the project, but "single shared password" would be unsatisfactory to me as a client.