ClickUp, Slack & Drive¶
Owner: Bryan · The working tools around the docs. Each has one job; keep them in their lane.
ClickUp: tasks and tracking¶
- Holds tasks, deadlines, ownership, and the per-client onboarding checklist (copied from a template per client).
- ClickUp tracks whether we did it; this manual explains how. Keep the checklist steps aligned with the Client Onboarding SOP so neither drifts.
- Durable decisions do not live only in a task comment. Record them in the relevant docs page.
Slack: discussion¶
- Fast decisions and day-to-day discussion.
- When a Slack thread settles something durable (a process change, a client rule), write it into the SOP or Gotchas. Slack is not the record.
- One channel per client; keep client-specific talk in the client channel.
Google Drive: files¶
- Files, exports, creative, and source assets.
- Client Shopify exports usually arrive here first, then get dropped into the client repo's
team-data/for the Data Refresh. - Version-controlled code belongs in GitHub, not Drive.
What goes where (quick reference)¶
| If it is… | It lives in… |
|---|---|
| A repeatable method or protocol | This manual |
| A task, deadline, or checklist item | ClickUp |
| A quick decision or discussion | Slack (then record durable ones in docs) |
| A file, export, or creative asset | Google Drive |
| Code or site content | GitHub |
| A client's KPI data or strategy | That client's gated hub |
| A credential or secret | The repo's gitignored personal-notes/ (or the password manager) |