Keep internal comments separate
from client feedback.
Your team discusses deadlines and costs on the same asset your client reviews, and you need to know which comments the client sees and where their answer comes back.
By the end, you’ll have posted an internal note and a client comment, seen what the portal shows your client, and found their review answer in the project.
Before you start
- A project with a client portal, with an asset out for client review.
- You’re a member of the workspace. The audience choice is shown to workspace members.
Watch the walkthrough
Keep internal comments separate from client feedback.
Harbor and Pine's key visual is out for client review. On the asset page, the Comments tab holds two kinds of comments.
Jordan's note has the Internal label. Only your team sees it.
Your note below it has no label. That's a client comment, and your client sees it in the portal.
Click Add a comment. Above the text, you choose who it's for.
Pick Internal for anything only your team should read, like a deadline or a cost.
Save. It gets the Internal label too.
For your client, leave it on Client, the default, and write it as you would to them.
This one has no label. You choose the audience when you post, and editing the comment later doesn't change it.
Now, your client's side.
Maya is signed in to the project's password-protected portal. She opens the key visual from her review.
Her Comments tab shows only client comments, under your workspace name. Neither internal note is here.
Her answer to the review goes in the Review tab: approve, or ask for changes.
Maya asks for changes on the key visual and submits her review. That step has a video of its own. Back in the studio, her answer is waiting.
A review answer isn't a comment. It comes back on the project. Under Needs attention, click View feedback.
Here is Maya's decision on the version she reviewed, and her reason.
The Reviews tab keeps the review. For each asset, it counts the client discussions, with internal notes left out.
In short: internal comments stay with your team. Client comments and your client's review answers are what the portal shares. Choose the audience before you post.
Search across all videos and guides.
Choose who a comment is for before you post it.
Your team and your client comment on the same assets. Some notes, like a deadline or a cost, are for your team only. In the video, Alex Morgan works on the Harbor & Pine key visual while it’s out for client review, and Maya Chen, the client, looks at it in the project’s portal.
Every comment has an audience: Internal, visible only to your team, or Client, visible to your client in the portal. Your client’s answer to a review isn’t a comment; it comes back on the project. Sign in to YetOnePro and open an asset to follow along.
- 01
Two kinds of comments
On the asset page, open the Comments tab. A comment with the Internal label, here Jordan’s note about the budget, is seen only by your team.
A comment without a label is a client comment. Your client sees it in the project’s portal.
- 02
Post an internal note
Click Add a comment.... Above the text, you choose who it’s for: Client or Internal.
Pick Internal for anything only your team should read, like a deadline or a cost, write the note and click Save. It gets the Internal label too.
To bring a teammate in on an internal note, see Mention a teammate in a file comment. - 03
Post a client comment
For your client, leave it on Client, the default, and write it as you would to them. After you save, it has no label.
You choose the audience when you post, and editing the comment later doesn’t change it. If a comment went to the wrong audience, delete it and post it again.
- 04
What your client sees in the portal
Your client signs in to the project’s portal, which is always password-protected, and opens the asset from their review. Their Comments tab shows only client comments, under your workspace name. No internal note is there.
Their answer to the review goes in the Review tab: approve, or ask for changes. For the client’s side, see Show your team exactly what needs to change and Approve work, or send it back with changes.
- 05
Where your client’s answer lands
When your client submits their review, the answer comes back on the project. On the project’s Overview, under Needs attention, click View feedback.
You see your client’s decision on the version they reviewed, and their reason. For the whole review flow, see Send work to your client for approval.
- 06
Check the Reviews tab
The project’s Reviews tab keeps the review. For each asset, it counts the client discussions on that version, across reviews: “Internal notes excluded.”
In short: internal comments stay with your team. Client comments and your client’s review answers are what the portal shares. Choose the audience before you post. To point at a spot on an image yourself, see Show exactly where an image needs changing.
Check the result
- Internal notes carry the Internal label; client comments have no label.
- You picked the audience above the text before you saved.
- You found your client’s answer under Needs attention, with View feedback.
- The Reviews tab counts client discussions per asset, internal notes excluded.
If it didn’t work
I posted a client comment that should have been internal.
Editing a comment doesn’t change its audience. Delete it and post it again with Internal picked.
Which comments does my client see?
Client comments, the ones without a label, show in the project’s portal under your workspace name. Internal notes never show there.
My client answered the review, but I don’t see a new comment.
A review answer isn’t a comment. It comes back on the project: under Needs attention, click View feedback, or open the Reviews tab.