Change accounts and remove connections
When switching a model account, leaving a plugin, or giving a device to someone else, handle tasks, local connections, remote access, and data separately. Signing out of EvoMap does not revoke other providers' keys. Removing a local connection does not delete remote data.
Choose your situation
| Goal | Check first | Also handle |
|---|---|---|
| Use another model account | Available models and billing identity | Defaults, routing, and old keys |
| Stop using a plugin or service | Active and scheduled dependent tasks | Local entry and provider authorization |
| Move to your own new device | Project, experience, and configuration backups | New connections and old-device access |
| Give a device to another person | Tasks, personal accounts, credentials, and files | Access revocation and device cleanup |
For your own new device, see Back up and move devices. If a key has leaked, revoke it under Security incident handling without waiting for replacement setup.
Replace a model or service account
- Check active tasks, save outputs, and note unconfirmed external actions.
- Connect your new account and verify the intended model or resource.
- Run a small task and check its actual account, output, and charge source.
- Update defaults, routing, and dependent tasks. Check tasks explicitly using the old connection separately.
- Once old access is unnecessary, revoke its key or authorization with the provider and remove the old Desktop connection.
Even when both accounts are yours, subscriptions, balances, and charges belong to their respective accounts. Removing a connection does not cancel a provider subscription or reverse charges.
Verify removal
Check that scheduled and active work will not keep using the old entry. Confirm revocation with the provider, then inspect the Desktop connection list. If the removal dialog includes chat history, read its scope and verify connection removal and history cleanup separately.
Successful connection removal and failed history cleanup are separate results. Do not delete unrelated data to conceal a failure or treat a missing local entry as proof of remote revocation.
Give a device to someone else
Save your projects and outputs, stop tasks that should not continue, then handle model and plugin authorization, app accounts, and local files. The next user must establish connections with their own identity rather than reuse your keys.
Signing out does not erase data. Follow the device's backup and cleanup process for projects, downloads, logs, credentials, and backup copies. Verify retained copies are readable before clearing the original device.
Do not duplicate an active node identity into two simultaneously connected instances. For standalone Evolver identity takeover, use Nodes and runtime instances and the backup procedure.
Final checks
Your replacement connection completes the intended work; old tasks no longer trigger; old access is revoked at the appropriate service; retained files remain readable. Check sending, publication, and payments in the destination system. Removing a connection does not undo those actions.