Every client's account and status. Business contact is for general business communications. Portal login is the address used to sign in and for portal access and security emails. They are independent. Click a row to view full details or correct any field, and search above to find one quickly.

Every active campaign case. Allen advances phase and status as work progresses — use the dropdowns to correct or override either one manually at any time.

Internal operating records for this case. Clients never see anything on this screen; they only receive deliverables you publish.

Reports and creative for clients. Create draft versions, then publish one when it's ready — internal drafts never overwrite what a client currently sees until you publish.

Client-submitted change requests. Allen classifies and executes routine ones automatically; click any row to reclassify, execute, deny, or reopen it yourself.

Client support tickets. Allen classifies, replies to, and resolves routine ones automatically; click any row to reply, reclassify, reassign, or close it yourself.

Each client's Meta ad account connection — the source of every lead. Allen checks these automatically and you can run a check anytime; reconnecting always requires the client's own Meta login.

Whether IDoMarketing's own automated systems are actually running. A service that stops checking in shows as Action Required, not Healthy — silence is never treated as fine.

Files shared with clients — reports, creative, brand assets. Upload one, then publish it when it's ready; publishing notifies the client, while review and withdraw stay internal.

To-dos for a client or for IDoMarketing internally. Create, reassign, complete, or cancel any task here — a new Client Action task notifies the client automatically.

IDoMarketing's own internal schedule — deadlines, App Review timelines, campaign launches. Never seen by clients. Click a date to add an event; task due dates appear as a read-only reference.

Client-facing research, scoped to one client's own selected objective. Draft here, review, then publish — a client only ever sees a published item for their own case, never a draft, never another client's research, never the underlying taxonomy.

No rule is active until you explicitly activate it. With zero active rules, every research item routes to your review — that's the correct starting state, not a gap.

Your own past review decisions, grouped by category/source/tier — the evidence base a candidate governance rule would be built from.

Volume, enumeration, and repeated-similar-query signals from real client search activity. A flag never blocks anything on its own except a sustained High-severity volume spike, which briefly slows that client's own requests — never other clients, never a silent permanent block.

What clients are actually asking. A "No match" row is a real research-gap signal — a real client question your published research doesn't yet answer — not an error.

Raw intake submissions and the Advertising Objective Records built from them. Preliminary objectives are not authorization to begin anything — only a Confirmed objective (finalized at the Discovery Meeting) unlocks Phase 2 Research for its case.

The client's raw, as-submitted answers. Superseded rows are kept as history, not deleted.

The governed, per-case source of truth. A client may have more than one of these over time — one per case, not one per client.