I was going to put this into my other thread about changing clients for a site but this is a topic of it's own... A database user is linked to a client. A database is linked to a site, and assigned a database user. When we change the client for a site, the client associated with databases users for that site are changed. Assume a database user is assigned to two sites for a client. Now move one of the sites to another client. The database user associated client is changed. But that user is still linked to a database for another site. Does the database user's relationship to one client or another affect their access to databases? I don't think it should, as an individual could be working on multiple databases for different clients, or there could be a single application in multiple client sites that uses the same database user to access a common database. So I was wondering if database users should be associated with a client at all. We can create database users that are not associated with a client - these get a "default" prefix. I've seen questions about this in the forum about how to override that icky prefix. There might not be a reason to associate a db user with a client except to standardize that prefix. If that's the case, then rather than setting the db user's client from the owner of one site to a new owner, I think it might be better to leave the user ID as-is and just remove the client association. Thoughts?