How Do I Remove a User from ChangePilot?
Hand over ChangePilot work, review shared access and verify offboarding without removing unrelated app permissions.
Applies to: a standard user of the Dataverse-based ChangePilot Enterprise App. Keep the user record and history; do not delete the person’s Dataverse record as an offboarding shortcut.
Before you start
A Power Platform administrator must review the ChangePilot environment, access routes and record ownership. If the user installed ChangePilot, administers it, or owns flows or connections, contact support@changepilot.cloud before removing access. Arrange the replacement connection or operational owner first.
If the environment or licence is shared with other apps, agree the scope with their administrators. Removing every role, team membership or licence can affect more than ChangePilot.
1. Hand over work and responsibilities
- Review the user’s open ChangePilot items and actions and reassign them to the agreed person or team.
- Check service-category ownership and nominated role recipients. Update Service Owner records and the role environment variables where the person is named. See role and category-owner configuration.
- Review user-owned Dataverse records with the administrator. Some tables are user/team-owned; others are organisation-owned. The Reassign Records command can affect records across the environment. Use it only when that broader handover is intended; otherwise have the administrator use an appropriately scoped reassignment process.
2. Remove the intended access
In Power Platform admin center, select Manage > Environments, your ChangePilot environment, then Settings > Users + permissions > Users. Review the user’s directly assigned security roles and team/group access.
Remove the access that grants ChangePilot use. Preserve roles and memberships needed for other apps unless the wider environment offboarding is intended. Permissions are cumulative: removing a direct role does not remove access inherited from a team. If one role or group grants access to several apps, ask the administrator to resolve that shared access rather than clearing everything.
3. Review the licence separately
Remove a Power Apps licence only if the user no longer needs the entitlement for other apps and your licensing administrator has confirmed the effect. Keeping a licence for another app is compatible with removing the intended ChangePilot access; licence removal is not the sole verification step.
4. Verify the handover
- Open ChangePilot work and service-category ownership now point to the intended successor.
- Role-recipient variables no longer target the departing user.
- Flows and connections still have an operational owner and run as expected.
- The removed user no longer has the intended ChangePilot access through direct roles or teams/groups; access required for other apps remains.
- If the whole environment access is being removed, confirm the resulting user state after synchronisation. Do not require a disabled environment record when access is intentionally retained for another app.
Microsoft references: security-role assignment and cumulative Dataverse access.
Documentation reviewed: 12 November 2026.