Stakeholders.

Spec access is invitation-only. There is no anonymous public link — every stakeholder you bring in gets their own private, named, time-limited portal. Open the Share panel from the project's right rail to manage them.

Why named, not public #

Earlier versions of SpecGraph generated public share tokens that anyone could open without identification. That made wishes from external reviewers anonymous and impossible to follow up on. The current model trades a click for traceability:

• Every portal visit is tied to a specific person, by name and email.
• Every wish a stakeholder files is stamped with their stakeholder identity, surfaced in the wish triage UI as a Stakeholder badge with their name, email, and organization.
• A revoked stakeholder's existing wishes stay in your queue but render as Stakeholder · revoked, so you know the source is no longer reachable.

If you need to send the spec to someone who'll never log in, this is how.

Inviting a stakeholder #

The Share panel has a single form. Required fields:

• Email — where the portal link is sent.
• Name — what shows in the wish triage UI and on their portal header.

Optional:

• Organization — surfaced on triage cards alongside the name.
• Department — pre-fills the wish form's department picker on their first submission.

If your workspace has an address book, the Pick from address book combo above the form fills all four fields in one click. Frequent reviewers (regulatory contacts, partner PMs, security auditors) belong in there.

Click Send invite and the portal link is emailed via Resend. The toast confirms when the email was queued; if the send fails, the row in the list shows a red "send failed" badge with the underlying error.

What the stakeholder sees #

A read-only spec view scoped to their project, plus a File a wish button on every captured phase. The full per-stakeholder experience is documented in Stakeholder portal — share that page with a stakeholder if they ask "what is this link?".

The portal shows what's been captured up to phase P-07 (Security). The handoff and progress phases are owner-only.

Managing the list #

The list below the form orders rows as active → pending → revoked, newest first within each group. Each row has three actions:

• Copy — copies the portal URL (/p/<token>) to clipboard. Useful when the email hasn't arrived and you want to send the link through another channel.
• Resend — issues a fresh token and emails it. The previous link stops working immediately, so use this if the recipient lost the email or the token may have leaked.
• Revoke — kills the token. The stakeholder's existing wishes are preserved, but they can't open the portal again. Confirms via dialog because this is one-way (you can re-invite them, but they get a brand-new link).

Expiry and self-extension #

Every link is good for 14 days from issuance. The stakeholder portal pings the server on each visit and auto-extends the expiry — an active reviewer never has to ask for a fresh link, but a forgotten one expires on its own.

Expired but not revoked? The row badge flips to expired. Resend mints a new token; Revoke closes the loop without emailing them again.

What stakeholders cannot do #

• See drafting-state internal commentary or interview transcripts.
• See the handoff (P-08) or progress (P-09) phases.
• See other projects in the workspace.
• See the team, audit log, knowledge base, or settings.
• Edit any spec field. The wish form is the only write surface they have.
• See other stakeholders' wishes — only their own, inline under each section and on the My wishes roll-up at the bottom.

When to use a stakeholder vs a workspace member #

Stakeholders never count toward your workspace member seat — they're a per-project, per-token relationship.

For workspace members, see Team & invites.