Client sharing
Share a live timeline or a captured snapshot with anyone on the client side. This page shows exactly what they see, what they can do, and what never leaves your team.
The client's view
Website relaunch
Live board share · refreshes every 20 seconds
Client sign-off · Nov 10Launch · Dec 7
Notes · visible to Halden Bank and Northwind
Marta Lindqvist Can the content migration start before sign-off for the blog pages?
Avery Chen Yes, the blog templates are separate. We'll start them on Nov 6.
Sign in to add a note
Visibility
Reviewers can't change the plan. A share has no editing controls; the only thing a reviewer can write is a note or a comment, when the share allows it. People are left off the timeline itself; an issue page opened through a share shows its assignee's name.
Access
Pick a preset when you create the share, or use Choose permissions to set each switch yourself. Turning on issue details opens the description and attachments of every issue on the timeline, so read them first.
| Preset | See the schedule | Open issues | Read notes | Write notes |
|---|---|---|---|---|
| View timeline only | ||||
| Comment on timeline | After sign-in | |||
| Review issues and comment | After sign-in |
Share link
Anyone with the link can view, without an account. To leave a note they sign in, with any account. Fluidwork shows the link once when you create it and stores only a hash, so copy it then. Links don't expire on their own: revoke them when the review is over.
Invitation
Fluidwork emails the invitation with your name, your organization, the timeline, and what it allows. Opening it requires signing in with that exact, verified email address. Resending issues a fresh link and retires the old one.
Either way, the token leaves the address bar as soon as the share opens, and revoking access takes effect on the reviewer's next request. An open live timeline stops updating within about 20 seconds.
Live or snapshot
Live timeline
The client sees the plan you last saved, refreshed about every 20 seconds while it's open. When a delay ripples through the dependencies, the new dates are what they see. Drafts never show until you save.
Snapshot
The schedule is frozen at the moment you captured it, with the capture date on the page. Later edits to the live plan don't move it. Issue details opened from a snapshot show current descriptions and comments; it's the schedule that's fixed.
When the client asks what changed, open the snapshot.
Capture a snapshot at kickoff or sign-off and give it a label. Later, open it from the timeline and every bar that has moved since is highlighted, with the snapshot and live start date and duration on hover and a count of changes. Milestone changes are counted too. The comparison is for your team; clients see the snapshot itself, not the diff.
The review loop
01
Reviewers who can comment drop a note on the timeline or comment on an issue they can open. Everyone you've shared that timeline with sees the same client-visible discussion, even through separate links.
02
Replies to a client's note are visible to the client. Everything else your team writes is internal by default, so you can agree the answer before you give it.
03
Reviews lists your active shares and the newest open notes. Threads where the client spoke last appear in the response queue on your dashboard for timelines you follow, and you follow the ones you create.
Questions
Unlimited reviewers on every plan