That’s not a “you” problem, it’s a platform limitation. Cloudways ties ownership roles too rigidly to a single account, which breaks a very common consultant workflow. You’re right: separating “owner” and “team member” across multiple projects should be standard like https://homehacksdecoradtech.com/.
Your workaround (second email) works, but it’s messy and scales poorly. The cleaner fix is pushing clients to keep ownership under their account and only grant you team access, but that still doesn’t solve the root issue.
That’s not a “you” problem, it’s a platform limitation. Cloudways ties ownership roles too rigidly to a single account, which breaks a very common consultant workflow. You’re right: separating “owner” and “team member” across multiple projects should be standard like https://homehacksdecoradtech.com/.
Your workaround (second email) works, but it’s messy and scales poorly. The cleaner fix is pushing clients to keep ownership under their account and only grant you team access, but that still doesn’t solve the root issue.