Updates, comments & files

Goal: keep your client in the loop on a project — post progress updates, discuss them back and forth, share files, and see what the client has been looking at.

Posting an update

Updates are dated notes your team posts to a project — think of them as a running log of progress ("Culled and edited, uploading to the gallery now").

  1. Open the project's page.
  2. Under Post an Update, type your message.
  3. Decide who should see it with the Internal note checkbox (see below).
  4. Click Post Update.

Some updates are added for you automatically as things happen on the project — creating the project, changing its status, linking or unlinking a release, and files being uploaded all drop their own entry into the same feed, so the project's history reads as one continuous timeline. These automatic entries are always client-visible (where Projects are shown to the client).

Internal notes vs. client-visible updates

Every update you post has an audience, set by the Internal note — visible to your team only, not the client checkbox on the form:

  • Checked (the default) — the update is an internal note. Only your team sees it; it never reaches the client's Updates feed, and the client's Ask Milo can't see it either. In the admin updates list it's tinted amber with a  Internal badge.
  • Unchecked — the update is client-visible and appears in the client's feed (as long as Projects are shown to clients — a company-level toggle).

Because the box starts checked, a post stays internal unless you deliberately share it. Existing updates from before this change remain client-visible.

Comments

Both your team and the client can comment — either as a reply under a specific update, or as a general comment on the project as a whole. Comments show under the update they were posted on, or in a separate Project Comments list for general ones.

Who gets emailed

Every comment sends an email to everyone involved on the project — all of the client's contacts and all of your company's team members — except the person who wrote it. There's no way to comment quietly; anyone posting should expect the other side (and their own teammates) to be notified.

See Notifications for where these show up in-app, and Emails not arriving if a comment notification seems to be missing.

Files

Either side can drag and drop files straight onto the project page — your team from the admin project page, the client from their own. Uploads count toward your company's storage the same as any other file; a client-uploaded file drops its own note into the update feed so your team notices it landed.

Files support most common types — video, images, PDFs, Office documents, ZIPs — up to 1 GB each.

Image files show as a thumbnail grid by default; use the List / Grid toggle above the files list to switch to a compact table instead. The same toggle and preference are shared with Client Assets.

Activity

On the admin side, the project page shows a merged Activity timeline combining your team's updates with the client's own views and downloads of that project's galleries and videos — so you can see, in one place, both what your team has said and what the client has actually looked at.

Alongside those updates the timeline now also merges in the project's discussion comments and its full task activity — tasks created, edited, status changes, assignments, and comments — plus project renames, brief edits, files added or removed, galleries or video collections moved between projects, and contract sends. Only your team sees this.

See Client activity log for how that view/download tracking works more broadly.

What clients see in their feed

Clients see the same updates and comments feed, with three things filtered out: updates you marked as internal notes, any activity about a model release, and anything referencing a gallery or collection that isn't published yet. This keeps their feed limited to things they're actually able to see elsewhere on the project.

Related