Integration rollout checklist
Test one account or action at a time. Expand the rollout after the pilot proves the expected access, blocked paths and a way back in.
Prepare the pilot
- Choose a disposable account or a limited pilot. Check the app, organization, environment and action before you enroll anything.
- Review the setup requirements. Record the working configuration and confirm who can restore it.
- Tell pilot participants which account and harmless action to test, which prompt to expect, and who can help if it fails.
Assign the roles your setup uses
Rehearse the setup
Use the checks that apply to your setup. For approvals, compare the account, action and result in the approval prompt and at the provider. See how to verify your setup before recording a result.
| Test | What to verify |
|---|---|
| Allowed action | Enroll on the pilot account. In a fresh session, run a harmless action and check that the intended credential or approval was used. Confirm the provider accepted the same action. |
| Below the threshold | If the setup requires multiple approvals, collect fewer than required. The action must remain unavailable. Meet the threshold with eligible approvers, then check the provider result. Some workflows require a separate execution step. |
| Blocked action | Use a disposable account or request to omit a required credential or approval. Check that the app blocks the test action and that no change was applied. |
| Independent recovery | Make the usual test device unavailable and use the documented backup. Check fresh access. When encrypted data is involved, verify that you can also open a harmless item. |
| Rollback | Use the documented steps and independent access to restore the prior test setup. Verify the intended access in a fresh session and check whether the test credential or policy is still active. |
Review rollout progress
Use one row per account and action. Record the pilot owner and test date. Enter Passed, Failed or Untested for each check. Use Not applicable for Approval result, Blocked test or Rollback only if that check does not apply.
If you only saw the integration listed or connected, keep the action Untested. See what counts as a verified result.
Keep passwords, recovery codes, QR codes and private keys out of the record.
Download a blank rollout record
The file stays in this browser. Blank or unrecognized check values need a retest.
- Checks passed
- Needs retest
- Failed a check
Expand or roll back
Expand in small groups after the applicable checks pass. Pause on a failed or untested access or recovery path. If access breaks, have the recovery owner follow the guide’s rollback steps before expanding. Repeat the access and independent recovery checks after replacing a device or changing the account, approval rule or recovery owner.
Retest a browser connection after a change →
Preview a change to the approval rule →
Choose an example
- Pilot an Okta access policy without locking out adminsRun the same test with a pilot user and a backup administrator so you know what your policy covers and how you can roll it back.
- Rehearse account recovery with 1Password and OktaCheck that your team can regain 1Password vault access when someone loses a device or access to Okta is interrupted.
- Test Cloudflare dashboard access with OktaCheck the complete access and rollback path on a dedicated test domain before requiring Okta for Cloudflare dashboard access.
- Replace a Keycloak one-time codeReplace a test authenticator in Keycloak. Check which sessions remain after you remove it, then verify that Keycloak rejects the old code and accepts the replacement.
- Replace Gitea and Forgejo sign-in codesReplace the authenticator for a test account. Check whether an existing browser session stays open, then verify that the old code fails and a fresh replacement code works.
- Troubleshoot a package release approvalIf your GitHub Actions workflow already waits for KeySigner approval before publishing to npm, use the request ID to see where the release stopped and what you can safely retry.
- Rehearse a two-owner approval in SafePropose a test payment with one KeySigner owner, confirm it with a second owner and verify what the Safe actually executed.
- Rehearse a Squads approval thresholdCheck that a disposable 2-of-3 Squad needs two independent approvals before a vault transfer can be executed.