> This would mostly stay the same. The users in a company could travel, but the choice of region is usually decided by where the company is located. For most o

> This would mostly stay the same. The users in a company could travel, but the choice of region is usually decided by where the company is located. For most of my apps, I have very little idea on their region aside from their login IP origin, and we get a high level of multi-region travels (like conference organizers). I'd encourage you to transform the notion of a tenant transfers from a 'major decision' to 'assume users will/should switch to closest tenant login'. It looks like your platform already allows this move-tenant-on-login approach, but I'd love to see more docs and more tests around that use-case.