How to let clients update monday.com items through a client portal

Let clients update selected and existing monday.com items directly from their client portal while your team keeps the underlying records and workflows in monday.com.

Use the navigation below to quickly jump to your desired section and learn more about each topic.

Clients do not always need to create something new. Often, the relevant project, request, account or task already exists as an item in monday.com and the client simply needs to provide or update part of the information. They might need to upload a missing document, change a requested date, add further details or update the current status of something they are responsible for.

One option is to collect every change through another form or email and then update monday.com manually. Another is to let the client update selected parts of the existing item directly through their client portal. With Client Portal Builder for monday.com, your team can keep managing the original items on its monday.com boards while clients interact only with the information you choose to expose. The result is one shared record behind the workflow rather than a separate client submission that needs to be reconciled with monday.com later.

Build client portals on monday.com

Client Portal Builder adds a dedicated client facing layer to the boards and workflows you already manage in monday.com. Share selected items, files and updates with clients and control where they can provide information or make changes.

Existing work

Update existing items instead of creating another request

A useful distinction is whether the client is starting something new or continuing something that already exists. If a client wants to submit a new project, request or piece of work, creating a new monday.com item usually makes sense. A monday.com WorkForm can collect the required information and create that item directly on the appropriate board. If the item already exists, creating another submission can make the workflow unnecessarily complicated. Imagine a request that is already being managed in monday.com. Your team does not need a second item simply because the client still has to provide a target date or upload a missing document. Instead, the client can update those fields on the existing item.

A simple rule is: Forms create new work, item editing continues existing work.

For workflows that begin with a new client submission, see our guide on collecting client requests with forms in a monday.com client portal.

Control

Choose what clients can update

Allowing clients to update an item does not mean giving them access to everything your team stores on that item or board. An internal board might contain information such as:

owner
internal priority
budget
team notes
internal deadlines
client supplied information
files
project status

The client may only need to interact with a small part of that information. For example, your team could display a requested completion date and supporting documents as editable while keeping ownership, internal notes and other operational columns available only inside monday.com.

Client Portal Builder lets you control which supported columns clients can edit. Current editable column types include Status, Text, Long Text, Number, Date and File columns. This makes item editing useful for workflows where the client should contribute information without being given unrestricted access to the underlying board. For the exact supported fields and configuration, see the item editing documentation.

Information

Collect missing information and files on existing items

One common use for item editing is completing information after an item has already entered the workflow. Consider a project request that already exists in monday.com. Your team already has the item and may already have assigned it internally. What is missing is information from the client. Through the portal, the client could provide the requested date, expand the project details and upload the relevant files.

There is no additional form submission for your team to match with the original request and no separate file exchange that needs to be copied back into monday.com. The client contributes the missing information to the item that already represents the work. This pattern can be useful for project collaboration, onboarding, document collection, account information and other workflows where information becomes available gradually rather than all at once.

Workflow

Keep client changes inside the monday.com workflow

The main advantage of editing an existing item is not simply that the client can change a field. It is that the updated value remains part of the monday.com item your team already works with. Imagine your team manages client projects with a Status column such as:

Information required → Ready to start → In progress → Client review → Completed

When additional information is required, the client can provide it through the portal. Your team sees the updated information on the same item and can continue the existing process from there. Dates, descriptions, files and other client supplied values do not need to live in another portal database and then be synchronized back into monday.com. The portal becomes another way to interact with the existing workflow rather than a separate workflow your team has to maintain alongside it.

Interaction

Use the right client interaction for each job

Item editing is only one way clients can interact with a monday.com workflow through a portal. The right approach depends on what the client is trying to do.

Create something new

Use a form when a client is starting a new request, project or process. The result is typically a new monday.com item, for example:

Submit new project request → Create new monday.com item → Team starts processing the request

Learn more about client request forms for monday.com.

Update something that already exists

Use item editing when the monday.com item already exists and the client needs to change or complete information on it, for example:

Existing project item → Client provides missing date and file → Existing item is updated → Team continues working with the same item

Make a predefined decision

Sometimes the client should not edit a field directly but instead take a clear action such as approving work or requesting changes. In that case, a predefined portal action can be more appropriate than exposing the underlying Status column for editing, for example:

Deliverable ready for review → Client selects Approve → monday.com workflow continues

We cover that pattern separately in our guide to client approvals in a monday.com client portal. Together, these interactions cover three common parts of an external client workflow:

Create new work → Forms
Update existing work → Item editing
Make a workflow decision → Actions and approvals

All three can remain connected to monday.com.

Example

Let a client complete an existing project request

Imagine an agency managing client requests on a monday.com board. A client has already submitted a new campaign request. The item now exists on the Requests Board with the following information:

Request: Q4 campaign
Client: Acme
Status: Information required
Target date: Empty
Additional details: Empty
Supporting files: Empty

The account manager reviews the request and realizes that several details are still missing. Instead of emailing the client and manually transferring the response back into monday.com, the relevant fields can be made available through the client portal. When the client signs in, they see their existing request and can:

add the target date
provide the missing campaign details
upload the supporting files

Those updates are made on the existing monday.com item. The account manager can then continue working from the completed request without creating another record or reconciling information from different systems. Later in the same workflow, the portal could display the progress of the request, provide completed files or let the client review a deliverable. The interaction changes as the item moves through the process, but the underlying monday.com item remains the same.

Access

Item editing is different from giving clients board access

Another way to let an external person update monday.com items is to invite them into monday.com itself. That can be the right approach when the external user should actively collaborate on a Shareable Board and work directly inside the monday.com interface. A client portal solves a different problem.

The client can sign into a dedicated client facing environment where you control which items and information are visible. Selected fields can be editable without exposing the rest of the internal board or requiring the client to work inside your team's monday.com workspace. For example, one shared project board could contain items for many clients. Your team works with the complete board internally, while each client sees only the items connected to them and only the information intended for their portal.

Whether guest access or a client portal makes more sense depends on how closely the external user should participate in your internal workspace. We compare the different approaches in our guide on sharing monday.com boards with external users and guests.

Summary

Let clients contribute without creating a second workflow

Client collaboration often involves more than showing information. Clients may need to provide missing details, upload documents, adjust dates or update other information after a project or request has already entered your monday.com workflow. When that happens, creating another form submission or collecting the change through email can leave your team maintaining multiple versions of the same information.

Item editing keeps the interaction attached to the monday.com item that already represents the work. Your team creates and manages the item in monday.com. The client sees the relevant information through their portal. The client updates the fields they are responsible for. Your team continues working with the same updated item. That creates a simple connected flow:

Manage the item in monday.com → Share selected information with the client → Let the client update what they are responsible for → Continue working with the same item in monday.com