Collins Approval Checklist 2026-06-30
Everything that needs Akash approval before a send, invite, permission change, external write, or live-system action.
Objective
Keep onboarding fast without accidental live control.
Why it matters
Account permissions, sends, workflows, and publishing are the real risk.
You need to
Approve only the first three now if ready. Hold the rest until proof. ~8 min.
Status
All approval items are held. CSV companion included.
Approve first, if ready needs you
| Approval | Default recommendation | Why |
|---|---|---|
| Approve candidate-facing email wording | Approve after one read. | Required before any outbound human communication. |
| Approve terms and start-date frame | $1,000/month, about 20 hours/week, 30-day trial, week-1 proof checkpoint. | Prevents scope drift into the $2,800 sprint quote. |
| Approve first-week source access | Share only the onboarding packet plus a scoped copy of the canonical VSL pack or a new raw clip. | Enough to start; avoids broad Drive/repo access on day 1. |
★ Default: approve the email, terms, and scoped file access only. Hold live tools until Collins ships the week-1 pack.
Hold until after week-1 proof held
| Approval | Default recommendation | Rollback | Ledger? |
|---|---|---|---|
| Workspace/repo access | Only if he needs local build work after the scoped pack proof. | Remove user/access; audit changed files. | Yes if external account or host access changes. |
| Google Drive folder access | Scoped content/build folders only. | Remove collaborator; audit shared files. | Yes. |
| n8n access | Sandbox or duplicated workflows first. | Remove user; disable duplicated workflow; restore before-image. | Yes. |
| GoHighLevel access | Test location or limited St. Pierre access first. | Remove user; audit workflows, contacts, calendars, messages. | Yes. |
| Database access | Read-only only if truly needed. | Revoke user/key/policy; audit queries if available. | Yes. |
| Canva access | Only if static polish needs it. | Remove team member; revoke shared designs. | Yes. |
| Loom workspace access | Let him use his own Loom first. | Remove workspace member. | Yes if St. Pierre workspace invite. |
| VEED/Submagic/fal access | Only after caption preset decision and cost approval. | Remove access; revoke shared project. Do not rotate credentials unless Akash asks. | Yes. |
| Instagram/YouTube/Meta access | No direct access in week 1. | Remove account permissions; review scheduled/published content and spend. | Yes. |
| ManyChat/DM automation access | No live access until comment-to-DM flow is scoped. | Remove user; disable draft trigger. | Yes. |
| Publisher/scheduler access | No scheduling/publishing until a review gate exists. | Remove user; clear scheduled queue. | Yes. |
Hard holds do not approve casually
- Credential/key/token sharing or rotation.
- Account-level permission changes beyond scoped invites.
- Outbound sends as Akash: email, SMS, DMs, or calendar invites.
- Live n8n or GoHighLevel workflow edits.
- Public publishing, scheduling, boosting, ad spend, or live comment/DM automation.
- Website, funnel, dashboard, or Cloudflare deploys.
- Database schema changes or production writes.
These require exact payloads and approval. If approved later, log them in Activity Ledger with before/after, rollback, and verification.
CSV companion reference only
- approval-checklist.csv has the same list in tracker format.
- access-tracker.csv has the tool-by-tool access tracker.
Path:
Projects/St_Pierre_Digital/Recruiting/Collins-Onboarding/approval-checklist.html