I'm afraid you've just discovered one of the reasons why a SQL Server service account should be the account under which the SQL Server service runs... and nothing else.  If you start also using it for client programs and such like, it's more likely to get locked out or otherwise compromised, potentially affecting the availability of live systems.  My advice is to ask for a new account(s) for those client programs.  It's more secure, as well - the more purposes to which you put an account, the more permissions you have to give it.

John