The client portal goes anywhere, as one embeddable page and inside HighLevel

The whole client portal became a single no-login page a partner can embed, arrived inside HighLevel, and reviewing work settled into one shape with explicit decisions and batched feedback.

The theme this week was the client side: where the client portal can live, and how approving and reviewing work feels.

For our partners

1. The whole client portal can now be embedded anywhere as one no-login page: overview and approvals, keyword mapping, plans, tasks, activity and reports, reached by a private per-client link the partner manages from the client’s Client Portal tab. Approvals and feedback work there exactly as they do for a logged-in client, with an optional email check for visitors.
2. The same portal is available inside HighLevel: agencies connect their HighLevel account, map sub-accounts to clients, and clients see their campaign (performance, plans, work feed, approvals, and a way to request a discovery) inside the CRM they already use.
3. Reviewing work got one shape: approve, request changes and decline are explicit choices, and feedback is a batch (highlight-to-comment on the piece, a notes list, one send-back). The decision lives in the sidebar, and approved content locks.
4. The approvals queue became a filterable table, grouped by section, with type and client filters on the all-clients view, and Google Business post items open as a full post: image, words, link and schedule.
5. The portal home became Overview, with a campaign intro the partner writes in their own words, and approvals got their own page.
6. Activity became the client’s work log, written in the partner’s voice (“your strategist”, never a robot), with plan approvals reading as alignment.
7. Campaign scope got a Configuration tab where each line’s client-facing wording can be overridden, and competitors moved onto the client’s Setup page.
8. Share pages wear the partner’s sidebar accent, discoveries and audits moved onto the shared data table, and team assignment on a client became a multi-select.

Behind the scenes

1. Which AI model an agent uses is chosen by our team, set per kind of task with a platform default behind it, so partners never pick or see one.
2. Staff can become the strategist for a campaign from the API: pull the same briefing the agent would get and work it by hand. Website tools joined the rest of the staff API, and the AI tools on a staff member’s own desktop can work the platform as them.
3. The scripts that move our book of agencies onto the platform learned its quirks: a live guest post lands as a closed link item, placeholder tasks are skipped, and everything brought across is attributed to our team rather than the partner’s.
4. Citations resolve a business’s category from its own data.
5. A platform-wide pause for rank alerts sits behind a staff switch for days when a data provider misbehaves.