Viewer Role Guide

Viewers observe. They see the roadmap, track milestone progress, and can leave a comment when they have something to add, but they do not vote on priorities, reorder the roadmap, or get anywhere near execution detail. The Viewer role exists for people who need visibility into a project without a stake in how it gets built.

Unlike the other four roles, Viewer is not a process role in the sense the rest of this guide series uses the term: it carries no defined responsibilities in planning, execution, or prioritization ceremonies. It is an access role, scoped down to the minimum: see what's happening, say something if needed, participate in nothing else.

This guide covers what Viewers can see and do. For the full permissions matrix, see User Roles & Permissions.

---

What Viewers See

GoalPath gives Viewers the same read-only project visibility as Stakeholders, minus the voting interface.

Visible to Viewers:

• Dashboard and project overview
• Roadmap (read-only): milestone sequence and status
• Milestones (read-only): scope and progress
• Alignment meeting view (read-only, cannot vote or advance stages)
• Team members
• Search

Not visible to Viewers:

• Kanban board and work queue (execution detail)
• Standup view (daily team mechanics)
• Time reports and velocity metrics (team performance data)
• Voting interface (Viewers do not vote on milestone prioritization)
• The planning view used to reorder the roadmap or sort by business value
• Individual item and subtask detail beyond what appears on milestones
• Project settings, billing, and member management

The one write action Viewers have: Viewers can add comments. It's useful for a client or external observer who wants to leave a note or ask a question without needing execution access.

This boundary is intentional. A Viewer who can edit or vote isn't a Viewer; at that point the right move is to upgrade them to Stakeholder or Collaborator, not to bend the Viewer role to fit.

---

Meeting Participation

Viewers are not core participants in any ceremony. GoalPath doesn't hide the alignment meeting from them, but they can't vote or control stage progression.

---

When to Use This Role

The Viewer role fits people who:

• Need to see project status without any operational stake in it
• Should not influence prioritization (if they should, use Stakeholder instead)
• Are external to the core team: clients, auditors, temporary observers, or leadership outside the immediate project
• Need occasional visibility, not a standing seat in the process

Common fits: clients checking on delivery status, auditors or compliance reviewers, executives outside the project's direct chain who want visibility without a vote, contractors whose engagement has ended but who still need historical access.

Start from Stakeholder, downgrade to Viewer. Most people added to a project have some stake in its priorities. If someone's involvement in prioritization ends but they still need visibility, that's the point to move them from Stakeholder to Viewer. See the Stakeholder Role Guide for what the extra access adds.

One practical note: Viewer is the only role that does not count toward billable project seats, which makes it the right default when granting access to someone outside the core team.

---

How GoalPath Supports This Role

GoalPath keeps the Viewer's surface area deliberately small. There's no board to misread, no estimate to second-guess, no vote to cast without context. The roadmap and milestone views give Viewers exactly the signal they need: what's planned, what's shipped, and how things are trending, without the noise of daily execution detail.

If a Viewer starts needing to weigh in on priorities rather than just observe them, that's a sign the role should be upgraded to Stakeholder, not that the Viewer role needs new capabilities.