For administrators
Move an app without breaking access
Use a pilot, keep a rollback path and verify the old login.
- Record the current deployed version, identity settings, storage ownership and backup state.
- Build the new integration in a separate test environment with separate data and secrets.
- Test invitation acceptance, an ordinary viewer, a scientist, revoked access and another workspace.
- Run the same workflow through each supported client. Verify results, saved decisions and usage.
- Rehearse a restore into an isolated target. Never overwrite working production data for a test.
- Promote a reviewed version only after its required checks pass. Keep the previous release and login settings available for rollback.
Changing an identity provider can change a user's subject ID. Do not assume matching email addresses alone safely remap historical record ownership. Preserve existing identity connections and use an explicit reviewed migration when needed.
