I work with DuoPlus, so this is written from inside that setup. But the checklist itself came out of a messy week, not a product page.
Last spring a contractor who handled two of our client stores finished her contract on a Friday. Her "work phone" was her own Android. Monday morning we realised three client logins, a 2FA app and a pile of saved drafts were on a device we had no right to ask for. Nobody did anything wrong. We just had no handover process.
Now every client gets its own cloud phone, and the account lives on that device, not on a person. When someone leaves, this is what we run:
- List the devices they had access to. In DuoPlus that's the team sharing view. If you use something else, keep a spreadsheet: device name, client, who can open it.
- Reassign before you revoke. Share the device with the person taking over first, let them open it and confirm the apps are still logged in. Same device environment, same login state, no re-entering anything.
- Remove the leaver's access. One click on our side. No factory reset, no "please delete the app from your phone" email.
- Check the region and proxy settings didn't drift. Each store runs in its own country setting. We look once, because a wrong region is the kind of thing nobody notices for a week.
- Rotate the passwords the leaver knew. The cloud phone doesn't fix this part. Do it anyway.
- Write one line in the client log. Date, who handed over to whom. Clients ask about it more than you'd expect.
The whole thing takes about 20 minutes per person now. It used to take a week of polite chasing.
What I'd still flag: it only works if the rule "accounts live on the client's device, never on a personal phone" is enforced from day one. Retrofitting it onto an existing team is the slow part.
If you want to try the same setup: https://www.duoplus.net (invite link: https://www.duoplus.net/share/market). Real Android cloud phones, each one an isolated environment, shareable inside a team.
