Operations portal
One approvals hub in place of scattered review threads
Two consumer brands were coordinating social content through DMs, shared docs and memory. SCOBOSS replaced that with a single private portal where planning, approval and reporting live together.
brands coordinated in clearly separated workspaces
2
approvals queue with an owner, a status and a history
1
every decision kept with an owner, a status and a history
Logged
At a glance
Content approval, planning and reporting in one gated workspace
A private client portal for coordinating social media management across two brands. Weekly reports, content planning, an approval queue and archives share one home behind access control, with shared state stored server-side so every stakeholder sees the same truth.
| Engagement | Custom internal portal for a client's two brands |
|---|---|
| Scope | Approvals, planning workspaces, weekly reporting, archives |
| Stack | Cloudflare Pages, Functions, D1, R2, Access, vanilla JS |
| Team | One builder, design through operations |
Situation
The breaking point
- Approvals scattered across DMs, email threads and shared docs, with no single source of truth.
- Status questions answered by asking a person instead of looking at a system.
- Two brands' work mixing in the same channels, raising the cost of every mix-up.
- History reconstructed from screenshots when a decision was questioned later.
Approach
The build
Give content review one home: every item has an owner and a status, every decision leaves a record, and both brands stay clearly separated.
SCOBOSS is a gated portal on Cloudflare Pages with Functions and D1 behind it. Content items move through an approval queue where each has an owner, a status and a history, and both brands get clearly separated workspaces under one login.
Weekly reports and planning state are stored in D1 as shared, server-side state rather than anyone's browser, so what the client sees and what the operator sees is always the same thing. Uploads live in R2, and Cloudflare Access gates the whole surface.

The moving parts
Under the hood
The core components that make the system work, and why each one matters.
Approval queue
Owner, status, history
Every content item carries who owns it, where it stands and what happened to it, so review stops living in chat scrollback.
Workspaces
Two brands, cleanly split
Each brand's planning and archive stay separate, with one shared operating rhythm across both.
Shared state
D1-backed, not browser-local
Reports and workspace state are stored server-side, so every stakeholder reads the same truth from any device.
Access
Gated at the edge
Cloudflare Access controls who can reach the portal at all, before any page loads.
What shipped
- Private portal behind Cloudflare Access
- Content approval queue with per-item history
- Per-brand planning workspaces
- Weekly report and summary pages with shared state
- Upload handling and archives on R2
Plugged into
- Cloudflare Pages and Functions
- D1 database
- R2 object storage
- Cloudflare Access
- Vanilla JS front end
The safety rails
- Access-gated at the edge, so the portal is never publicly reachable
- Server-side shared state, so no stakeholder acts on a stale local copy
- Decision history kept per item instead of in chat scrollback
- Plain, dependency-light code the owner can keep running cheaply
Outcomes
The payoff
Review stopped being a chase across channels and became a queue with owners.
The client answers their own status questions by looking, not asking.
Both brands run on one rhythm without their work ever mixing.