Controlling what clients can see

Visibility is the core thing that makes LyncView different from giving a client a shared spreadsheet. You decide, task by task, what they can see.

Levels of visibility

• Visible. The task appears in the client's portal with its title, due date, and current status.
• Hidden. The task is completely invisible to the client. They don't know it exists.

Default visibility

Set a default for each item in your template. As a rule of thumb:

• Make visible: milestones, decisions, anything the client is waiting on, anything that affects their timeline.
• Hide: internal coordination tasks, reminders to follow up with third parties, notes-to-self, anything that'd make the project look stuck when it isn't.

Overriding per-project

On any project, you can override the template defaults. Click the visibility toggle next to a task. Use this when a specific client has different expectations than the norm.

Why not just show everything

This is the most common mistake new users make. The instinct is "more transparency is always better." In practice, showing every internal task gives clients false signals — they see a task labeled "follow up with John" sitting open for two weeks and conclude their project is stuck, when really, that's just normal coordination work that happens in the background.

The portal is most effective when it shows clients exactly what they care about — milestones, blockers, what's next — and hides the operational mechanics.