Viewport Docs

Roll out Viewport to a team with clear roles, scoped integrations, approvals, and run evidence.

Team setup should move from narrow proof to broader usage. Do not start by connecting every repo and channel.

Rollout Order

Create an organization.
Invite teammates.
Set up teams.
Pair a self-hosted worker.
Connect Slack and GitHub.
Create one small workflow.
Prove a first run with approvals, PR/proposal, Slack receipt, and audit.
Broaden repos, routes, and context sources only after the first proof.

Team Surfaces

Provider integrations

Connect Slack, GitHub, and runner-side credentials for the launch path.

Slack

Use Slack as a trigger and notification surface, with Viewport as source of truth.

Approval policies

Define who reviews plans, implementations, and side effects.

Audit log

Review the evidence left by runs and decisions.

Roles

Keep v1 simple:

organization owner/admin/member;
team owner/admin/reviewer/member.

Team workflows should use team-level policy and explicit governance settings. Avoid hidden risk engines and workflow-specific user overrides for the launch path.

What Good Team Setup Looks Like

one worker paired and claimable;
one sandbox GitHub repo connected;
one Slack channel connected;
one published workflow;
reviewer tags or team roles configured for gates;
denial paths tested for unauthorized publish, repo, provider, and team access;
run detail understandable without raw logs.

For teams