Let Clients Update Notion From Their Portal (Without Workspace Access)

A read-only client portal is a great start: clients can see their projects, tasks, and documents without you sending screenshots or scheduling a call. But real client work is a conversation. Clients need to approve a deliverable, mark a task as reviewed, pick an option, or leave a quick note — and every time they do that over email, someone on your team has to copy the answer back into Notion by hand.

Editable fields close that loop. You choose specific properties a client can change, and their update writes straight back to the same Notion page — no Notion seat, no access to your workspace, and no manual re-entry.

What clients can edit

You stay in control of exactly which properties are editable. Everything else remains read-only. Today, clients can update these Notion property types from the portal:

• Status — move an item through your workflow (for example, from In Review to Approved).
• Select — pick from the options you already defined in Notion.
• Checkbox — toggle a simple yes/no, like Approved or Received.
• Number — enter a quantity, score, or budget figure.
• Rich text — leave a short note or comment.

A field has to be visible in the view before it can be made editable, so nothing becomes editable by accident. Titles, dates, relations, and other structural fields stay read-only.

Why this matters for agencies

Two-way editing turns your portal from a status page into a workspace your clients actually use. That means fewer status-check emails, faster sign-off, and a Notion database that reflects reality because the person with the answer updated it directly.

• Approvals happen in one click instead of a thread of replies.
• Your Notion stays the single source of truth — no shadow spreadsheets.
• Clients feel ownership without ever touching your workspace.

Keeping it safe

Letting anyone write to your Notion sounds risky, so every edit is checked on the server before it reaches Notion. Portalize confirms the logged-in client actually owns the record — using the same per-client scoping rules as the view — so a client can never edit a row that is not theirs, even if they guess a page ID. Status and select changes are validated against the real options in your database, and unsupported field types are simply not editable.

You can also turn on a Client Field Updates notification to get an email whenever a client changes an editable field, so nothing slips by unnoticed.

How to set it up

In the Portalize view editor, open the Fields tab, make a property visible, then check it in the Client Editing section. Save the view, and clients will see inline controls on list, table, card, and detail pages. Start with one field — a task Status is a great first candidate — then expand from there.

Your Notion workspace stays exactly as it is and remains the source of truth. Portalize just gives each client a safe, scoped way to keep it up to date.