Client portal for agencies: what to put in it, what to leave out, and how to roll it out

Every agency gets the same emails. Can you resend that invoice? Which version of the contract did we sign? Where are we on the website? Who do I send this bug to? None of them are hard to answer. Together, they take hours every week, and they make your team look less organized than it is.

A client portal fixes that by giving each client one signed-in place for the things they keep asking about. Done well, it reduces email, speeds up approvals and makes a small agency feel established. Done badly, it becomes another login nobody uses, or worse, a window into things the client was never meant to see.

This guide covers what belongs in an agency client portal, what does not, and how to roll one out so clients actually use it.

What belongs in a client portal

Start from the questions clients ask most, and put the answers where they can find them without you.

Invoices

Clients should be able to see every invoice you have sent them, its status and the amount due, and download the PDF. This alone removes a large share of “can you resend” emails, and it helps the person on the client side who has to forward invoices to their own finance team.

Documents

Signed contracts, statements of work, briefs, brand guidelines and final deliverables. The rule of thumb: if a client might reasonably ask for it again in six months, it belongs in the portal.

Project status

A view of the projects they are paying for: what is in progress, what is done, what is waiting on them. Clients do not need your full task board, but they do want to know where things stand without scheduling a call.

Requests

A single way to ask for something: report a problem, request a change, submit a brief through a form. Requests that arrive this way have an owner and a status, so they do not disappear in someone’s inbox.

Approvals

Anything that needs a client decision (a deliverable, a change, a document) should be approvable in one click, with the option to reject or ask for changes. That leaves a record of who approved what and when, which is useful when scope questions come up later.

Answers to common questions

A short knowledge base with how-tos and FAQs saves your team from answering the same question for every client.

What to leave out

Just as important is what the client should not see.

• Internal notes and comments. Anything written for the team, including frank assessments of the client, stays internal.
• Rates, margins and costs. Your internal cost rates, commissions and project profitability are your business.
• Every task. Showing all 140 tasks invites micromanagement. Share milestones and client-facing tasks, not the internal checklist.
• Raw time entries, unless you bill hourly. For time-and-materials clients, a time summary can build trust. For fixed-fee clients, it often starts a debate about hours that do not affect the price.
• Draft documents. Share the version you want them to read, not the one still in review.
• Other clients’ anything. This sounds obvious, but it is the real test of a portal’s permission model.

The principle: share outcomes and decisions, keep process and economics internal.

How to roll it out

A portal only works if clients use it. A few habits make the difference:

1. Start with one or two friendly clients. Ask what they would want to see, then adjust.
2. Preview before inviting. Look at the portal exactly as a client will before anyone else does.
3. Invite the right people. Usually the day-to-day contact plus whoever handles invoices on their side.
4. Make sign-in effortless. A magic link sent to their email beats yet another password.
5. Point to the portal in every email. “The invoice is in your portal” teaches the habit faster than any onboarding message.
6. Stop attaching things to email. If the portal is the source of truth, behave like it.

How SparkDesk’s client portal works

The SparkDesk client portal sits on the same record as everything else (the account, its projects, invoices, documents and cases), so there is nothing to sync. It is included from the Solo plan up.

Sign-in

Clients sign in with a magic link sent to their email address, or with a password if they prefer. There is no app to install.

What clients can see and do

What appears depends on the portal role you give each client contact. Roles turn on capabilities individually, so you choose, for example, whether a contact can:

• See their invoices and download the PDFs.
• Open shared documents, and upload files.
• Follow their projects: overview, client-facing tasks, project documents and, if you choose, a time summary.
• Submit requests as service cases or through forms, and see their status.
• Review approvals and approve, reject or request changes.
• Read your knowledge base articles.
• Manage their own profile and notification preferences.

That means a client’s finance contact can see invoices without seeing project tasks, and a project stakeholder can approve deliverables without seeing invoices.

Branding and preview

In Settings, the Client Portal page covers portal access, the homepage, branding and roles. A Preview shows the portal and your knowledge base articles exactly as a client will see them, before anyone is invited.

Requests and the service desk

Requests submitted in the portal become cases in the service desk (starting on the Team plan), with an owner, a priority, a status and SLA tracking. Your team replies from SparkDesk and the client sees the reply in the portal. See the service desk features for more.

Seats

Client portal users never take a paid seat. Each plan includes a number of portal users, and you can add more in packs. Details are on the pricing page.

What the portal does not do

Clients can view and download invoices in the portal, but they cannot pay them online through SparkDesk. SparkDesk records payments when they arrive; it does not collect them. The portal also does not offer booking links for meetings.

A simple starting setup

If you are setting up a portal for the first time, this configuration works for most agencies:

Portal role	Sees
Client lead	Projects, documents, requests, approvals, knowledge base
Client finance	Invoices and documents
Client stakeholder	Approvals and project overview

Begin there, watch which questions still arrive by email, and adjust. Our guide to choosing a CRM for agencies covers how the portal fits with the rest of the client lifecycle, and the client portal feature page has more detail.

Try it with one client

Set up a portal role, preview it, and invite one client contact. Start a 14-day free trial, no card needed.