Agency operations playbook
A copyable SOP for agency teams: every proxy credential lives in the team vault - never in a spreadsheet or chat message - with a named owner, a trigger, a checklist, and measurable signals.
Quick answer
Every proxy credential lives in the team vault - never in a spreadsheet or chat message. Owner: Operations lead (vault admin). Trigger: Immediately for any new credential; access reviewed monthly. Work the checklist top to bottom and record every change with a date.
A copyable SOP for agency teams: every proxy credential lives in the team vault - never in a spreadsheet or chat message - with a named owner, a trigger, a checklist, and measurable signals.
Every proxy credential lives in the team vault - never in a spreadsheet or chat message. Owner: Operations lead (vault admin). Trigger: Immediately for any new credential; access reviewed monthly. Work the checklist top to bottom and record every change with a date.
Trigger: Immediately for any new credential; access reviewed monthly. Cadence: as triggered, reviewed monthly.
| Objective | Every proxy credential lives in the team vault - never in a spreadsheet or chat message |
|---|---|
| Owner | Operations lead (vault admin) |
| Trigger | Immediately for any new credential; access reviewed monthly |
| Cadence | On trigger; monthly review |
| Records kept | Dated log entry per change |
Facts last reviewed 2026-09-01.
If a checklist step fails twice, the operator escalates to the team lead the same day. The team lead decides between a rollback and a scheduled fix, and records the decision in the runbook. Unresolved after 48 hours: escalate to the vendor's support with the incident notes attached.
In a password manager or secrets vault with role-based access. Spreadsheets and chat messages copy without control and leak without notice.
Operators who run profiles need read access; leads need write access. Review the list monthly against the team roster.
Buy self-serve now, or talk with us about a larger agency inventory.