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

  1. Choose a disposable account or a limited pilot. Check the app, organization, environment and action before you enroll anything.
  2. Review the setup requirements. Record the working configuration and confirm who can restore it.
  3. 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

Setup owner
Confirms the exact account and enrollment, and records which actions require review.
Requester
Starts a harmless action from the pilot account and checks what the provider did.
Approver
Reviews the request details and checks which people or keys count toward the configured rule.
Recovery owner
Uses an independent route and checks that someone can restore the previous setup.

Record the independent recovery route →

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.

TestWhat to verify
Allowed actionEnroll 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 thresholdIf 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 actionUse 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 recoveryMake 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.
RollbackUse 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

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 →

Restore a previous signing rule →

Hand off approval access →

Verify an approval and its result →

Choose an example