The operating problem
Start with a quarterly client-system access review. A successful handoff produces an approved access list and a verified change record. Define the accountable owner before connecting systems. Revocation requires explicit authorization and an operational impact check. A source event is a request to evaluate the current state; it is not permission to make an irreversible change.
Use your own working copy
The free workbook for this process opens in a browser and works offline after download. It includes editable checks and notes, a text export, and a print view. It is a planning resource: it does not send messages, read account data, or run actions in business systems. No vendor account is needed to use the workbook.
Map the process
1. Inventory approved connections
List scoped user accounts, integration identities, tokens, and their owners without exporting secrets.
2. Compare active engagement needs
Check current staff assignments and the least permissions required for each service.
3. Flag stale access
Identify departed staff, unused keys, shared accounts, and owners who cannot be confirmed.
4. Review the change plan
The engagement owner and administrator approve removals, replacements, and rotation windows.
5. Verify continuity
After authorized changes, test permitted access and record that the old access no longer works.
Information to check
These reference fields describe the process. Use invented values while planning. Keep real records in an appropriate private system; the public website does not need them.
| Reference field | Working record | Check before progressing |
|---|---|---|
| system_id | system_id | Resolve the stable source reference in the correct client, entity, and engagement. |
| principal_id | principal_id | Resolve the stable source reference in the correct client, entity, and engagement. |
| credential_owner | credential_owner | Use the authorized owner or reviewed decision; unknown values stop the handoff. |
| review_decision | review_decision | Use the authorized owner or reviewed decision; unknown values stop the handoff. |
Acceptance checks
- An ownerless integration is flagged.
- A planned revocation includes the affected workflow owner.
- A repeated source event creates only one current review task.
- A changed source version invalidates an earlier approval.
Walk through a successful example, a duplicate, a missing item, an incorrect match, and an interrupted handoff with synthetic records. Record the expected result, observed result, owner, and recovery action. Checklists record your work; checking a box does not establish that an external action happened.
Ownership and review
Name the person responsible for the process and the person who can resolve an exception. Define which decisions require qualified professional review. Use stable references, limit access to private records, and document when work must stop. Educational material does not establish legal, accounting, tax, security, or regulatory compliance.
Run a measured pilot
Choose a small, reversible sample. Measure handling time, waiting time, review, rework, and errors before changing the process. Include the effort of maintaining the new method. Expand only when the observed result meets your acceptance criteria; a longer checklist is not proof of improved performance.
Use the free workflow planner to define your next step, or compare the assumptions in the opportunity calculator.