For teams
For teams
Set up Viewport for a group. Shared workflows, approval routing, audit logs, Slack and webhook integrations.
This section is for the person rolling Viewport out to a team. You go beyond the solo loop: shared workflows, who-decides-what policies, audit visibility, and integrations.
The team setup arc
A typical rollout takes about half a day on the platform side, plus time per developer to install vpd.
- Create an organization. Your tenant boundary.
- Invite teammates. By email, with role.
- Set up teams. Org-local groups for routing.
- Share resources. Workflows, plans, vaults.
- Approval policies. Auto-approve thresholds, gate routing.
- Audit log. What's logged, retention, export.
Integrations
Slack
Route inbox events to a channel. Approve from Slack directly.
Webhooks
Subscribe your own consumer to inbox + audit events with signed delivery.
What's coming
How it differs from the solo path
Same daemon. Same agents. Different posture:
| Solo developer | Team |
|---|---|
| One workspace, one human | Multi-member workspace |
| You decide every inbox item | Routing by role, team, or share group |
| Inbox is your own list | Inbox is a shared queue, first-resolves wins |
| Workflows live in your head | Workflows in .viewport/workflows/ and shared |
| Audit log is informational | Audit log is compliance-grade |
| Notifications: phone push | Notifications: phone, Slack, webhook |
You can grow from solo to team without changing the daemon. The daemon's organization binding is configurable per machine. See Concepts: Organizations and teams.