Client portals: involve clients without giving up control

A portal is a curated landing page for one client. You add the resources they should see (reports, monitoring projects, campaign builds) with per-item labels, descriptions, and ordering, then send a single invite. The portal carries the client's branding (or yours), and its content stays live: the report a client opens in the portal always shows current data.

Invited clients register once and get an external-viewer account: their own login, read-only, limited to exactly the resources shared with them, with filtered fields and a viewer-appropriate agent. On a shared monitoring project they see the same configured metric columns as you, plus a built-in glossary that explains every metric in plain language, which cuts the “what does ROAS mean?” calls.

On shared campaign builds, clients comment on specific elements (a headline, a description, a keyword, an image) as annotated feedback threads with statuses (open, in review, resolved). Your team is notified via an hourly feedback digest email, and the AI generates ready-made alternative copy from the feedback. Review rounds become asynchronous and traceable instead of a call plus a spreadsheet.

Organizations support multiple users with the roles Owner, Admin, Editor, and Viewer, at organization level and separately per resource: each project, report, campaign build, portal, and branding has its own access list. Email invites carry a role, a personal message, and an expiry; domain-based auto-join brings colleagues in automatically. There is no per-seat pricing anxiety: users and clients are unlimited.

Two layers. Organization branding puts your logo and name in the app's sidebar, so your team works in your tool. Client brandings are reusable design configurations (colors and logo, extractable automatically from the client's website URL) applied to shared views, reports, and portals. Your client sees their brand and yours, never ours.