Client portal for account managers

Each brand’s client portal replaces the status sheet you used to keep by hand. Clients see their work as it moves, and you choose what they see. This page is for account managers.

Open the Client portal tab

Open the brand and pick the Client portal tab. It shows to the brand’s account managers only. It has two parts, Clients and Settings, and an Open client portal button at the top.

Manage the brand’s clients

Clients is one table, a row per contact: their name and How they get updates (through their account team, or in the client Slack channel). Every contact can do everything in the portal: approve work, request changes, view work and fill forms. There are no roles to set.

Status stays empty while all is well. When something needs you, it names it, and the row’s one button fixes it:

Not signed in yet - they have not used an invite. Click Invite, then send them the link.
No email yet - they need an email before you can invite them. Click Add email.
Access removed - they can no longer open the portal. Click Invite to let them back in.
Can’t be tagged in Slack yet - MX has not found them in Slack, so client channel updates do not tag them. Check their email matches their Slack account, then save it again in Edit.

Hover a status to read the whole sentence. Everything else is in the row’s More actions menu: Edit, API keys, New access link, Calendar link, Revoke access and Remove.

Edit opens the contact in a dialog. How they get updates saves as you change it. Changing a saved email signs them out, so MX asks first.

Add contact opens the same fields for a new contact.

Choose what clients see

Under Settings, every change saves as you make it:

Opens on - the view the portal opens on, for clients and for you. Saved views sit beside the built-in ones.
Columns - the columns of the work table you can hide: Type, Last updated, Note and Links. Name, Status and Launch date always show.
Tabs - the parts of the portal you can hide: Activity, Analytics and Files. Work always shows, because it holds what needs the client. Analytics shows the brand’s Klaviyo campaign and flow numbers, so it is empty until Klaviyo is connected on the brand’s Connections tab.
Client API - lets clients create API keys so their developer can pull their work into other tools. Off until you turn it on. The API guide link explains it.

A hidden column is held back everywhere: in the table, in Activity, in CSV and PDF exports, and in the API.

Work in the portal

Click Open client portal to open the brand’s portal itself, the page your clients use. You see and act on it as a client does: you can Approve or Request changes, save, rename or delete views, download the CSV and print the report. A bar at the top says Well Copy team: you see and act on this portal as the client does., and Back to MX returns you to the Client portal tab.

Needs you shows you every form the brand’s clients still owe, whoever it was sent to, with Answer turned off: only the client it was sent to can answer it. Each client sees only the forms sent to them.

The first decision on a review settles it for everyone, client or team. The task then shows who decided and when, and Activity names them, for example Approved by Dana (Well Copy).

Saved views belong to the brand: the brand’s clients and its account team share one list, so a view you save shows for every client, and a view a client saves shows for you.

API keys belong to a contact, so the portal does not offer them to you; manage them from the contact’s row in Clients.

On Files you see both kinds of file, each row marked: what the brand’s clients sent through forms (From the client) and the brand’s own files (From Well Copy). Clients see only the files clients sent.

Which work clients see

Clients see the brand’s campaigns, flows, flow updates, SMS and text campaigns, scheduled or not. Deleted work and proposals not yet agreed stay out, and so does other work.

On a task, the Client portal group sets Visibility: Auto shows campaigns, SMS and flows, and Show or Hide overrides that for the task (for example, show an A/B test). Next to it, the task says Clients see this or Hidden from clients. Note for clients is the task’s standing note to clients; it saves as you type. Internal notes, comments, people and internal statuses never reach the portal.

Waiting on the client

When a task needs something from the client, open Waiting on on the task and pick The client under Who owes the next step. MX then asks What the client needs to do, for example Send the gift photos, and Save stays off until you write it, every time you set it. The client reads that line in Needs you next to Waiting on you, and on the task as What we need from you, even when the Note column is hidden. It is separate from Note for clients, and it goes away when the task stops waiting.

Client API keys

When Client API is on, a contact can hold API keys once they have signed in. Open API keys from the contact’s menu, enter a Key name and click Create key. Copy the key right away with Copy key: it is shown only once. Revoke stops a key at once.

Clients can also create their own keys from the portal. Send their developer to Client portal API.