Skip to main content
Projects are what a client sees first. When a contact signs in, the portal opens on their project list – every project of their client company that is shared with them. Access follows the project’s client automatically. Move a project to a different client and the access moves with it.

​
How a project becomes visible

A portal contact sees a project when both are true:
  1. They are a portal contact of the client company, and
  2. A share exists between them and the project.
Shares are created two ways.

​
Automatically, from the project’s client

This is the normal path and it runs in both directions.
Moving a project between clients changes who can see it. The old client’s contacts lose it at the same moment, so nothing leaks – but check the new client’s contact list before you move a project, because they will see it immediately.

​
By hand, per contact

On the client record’s Portal access panel, each contact has a checkbox for each of that client’s projects. Untick one to take a single project away from a single contact.
Archiving a project does not remove portal access. An archived project a contact is shared on stays in their list. Untick it if you want it gone.

​
What the portal project list shows

The list is the portal home page. Its heading reads Shared with you, above the eyebrow Your projects. Each project is a card, not a table row. A card shows exactly three things: There is no search box, no filter, no sort control and no pagination on the portal project list. When nothing is shared yet, the client sees Nothing shared yet with the text Your group hasn't shared any projects with you. You'll see them here once they do.

​
What the portal project page shows

Clicking a card opens the project. At the top is a back link, All projects, then the project name and its status badge. Below that is one card per client-visible deliverable. Each deliverable card shows:
1

The deliverable title

The task title, exactly as you wrote it.
2

A status badge

Only three values reach a client – To do, In progress or Completed. Your internal sections are collapsed into these before they leave your workspace.
3

A due date, if one is set

Shown as Due 14 Mar 2026. Nothing renders if there is no due date.
4

An approval button

Approve deliverable, or the word Approved with a tick once it has been approved.
5

A comment thread

Every client-visible comment on that deliverable, plus a box to add one.
6

An attachments row

An Attachments label and an Upload file button.
A project with nothing to show reads No deliverables yet with the text There's nothing to review on this project right now. Check back soon.

​
Approving a deliverable

A client can sign off on a deliverable in one click.
1

Click Approve deliverable

The button sits on the deliverable card.
2

Confirm

A dialog opens: Approve deliverable? with the text Your group will be notified and this approval is recorded. This can't be undone from your side. The buttons are Cancel and Approve deliverable.
3

Done

A toast confirms Approval recorded. Your group has been notified. The button is replaced by Approved with a tick.
There is no undo in the portal. A client cannot un-approve a deliverable themselves.
Approving is safe to repeat – clicking twice does not record two approvals.

​
Uploading a file

The Upload file button takes one file at a time. While it uploads, the button reads Uploading… and is disabled. On success a toast confirms Uploaded brief.pdf.
The Attachments row lets a client upload, but it does not list files that were uploaded before. A client cannot browse, download or delete attachments in the portal.
There is no drag-and-drop in the portal, and no multi-file selection.

​
Example

Northwind Studio moves the Brand Refresh project from Fenwick Legal to Bluebird Coffee, because Bluebird acquired the brand work. The moment Priya Raman saves the change:
  • Fenwick Legal’s portal contacts lose access to Brand Refresh.
  • Ruth Castillo, Bluebird Coffee’s contact, gains it.
Ruth signs in and now sees three cards – Website Redesign, Monthly Retainer and Brand Refresh. She opens Website Redesign and sees a deliverable “Homepage wireframes”, marked In progress, due 14 March. She approves it, and Northwind is notified.

​
Permissions

Sharing needs the Client portal app to be on. Unsharing does not – you can always take access away, even with the portal switched off. Every grant and revoke is written to your audit history.

​
Common questions

The client record’s checkboxes only list that client’s own projects, so this is not something you do from the portal panel. Access is designed to follow the project’s client.
No. Only tasks marked client-visible appear. Everything else stays internal.
No. The portal is read-only apart from approving, commenting and uploading.
Archiving hides a project from your team’s lists but does not revoke portal access. Untick it on the client’s Portal access panel.
No. The portal project list has no controls at all – it is a plain list of cards.

​
Troubleshooting

What clients can see

The full field-by-field list.

Portal comments

Client-visible comments and how notifications are grouped.

Invite a client contact

Give a client a login.

Client projects

Projects on a client record.

Project visibility

Who on your team sees a project.

Remove portal access

Take access away cleanly.