Viewport Docs

Spin up your team's tenant. Owner, members, the org switcher, and what comes for free on creation.

An organization is your tenant boundary in Viewport. Every member, machine, workflow, plan, inbox item, vault, and audit row belongs to exactly one org. Orgs cannot see each other.

Create one

In the web app, click the org chip in the top-left → Create new organization → name it.

Acme Engineering         ← the human-readable name
acme-engineering         ← auto-suggested slug (lowercased, hyphenated)

What happens behind the scenes:

A workspace row is created with a ULID id, your owner_id, and your name as the slug seed.
A membership row is created with role owner.
An audit event workspace.created is written.

No team is auto-created. No personal team. The org starts at zero teams, zero machines, zero workflows, zero data. A clean tenant boundary.

First-run onboarding can create the initial team in the same flow. That team is still explicit: you name it, and you can optionally attach the team's primary Git Resource so .viewport/ exports have a durable repository target from day one.

Naming guidance

The name is what teammates see in the switcher. Use the name they'd recognize.
The slug appears in URLs (getviewport.com/acme-engineering) and is mostly cosmetic. Routing internally uses the ULID.
Slugs can change later without breaking links. Internal routing key is the ULID, never the slug.

What you can do immediately

The moment the org exists, you can:

Invite teammates. See Invite teammates.
Pair a machine. From any laptop, run vpd pair and choose this org in the browser flow.
Create teams. Optional. See Set up teams.
Create your first workflow. Commit a YAML file or use the in-app editor.

Multi-org members

A single human can belong to multiple orgs (work + personal + OSS, for example). Each membership is independent:

Different roles per org.
Different team memberships per org.
Different default views.
Different machine pairings per org (a single daemon can pair to multiple orgs with per-org crypto identity).

See Concepts: Organizations and teams for the full model.

Switching orgs

The chip in the top-left is the switcher. Click → list of orgs you belong to → pick one. The UI shows a fullscreen transition while tenant state flushes; landing in the new org is a clean state.

Active org indicator   ◇ Acme Engineering ▾
                            │
                            ▼
                       Org switcher panel
                            ├── Acme Engineering  (active)
                            ├── Personal
                            ├── OSS Maintainers
                            └── + Create new organization

Org-level settings

The owner (and admins) can configure:

General: name, slug, default avatar.
Members: invite, role-change, remove.
Teams: create, archive.
Workflows: shared definitions.
Notifications: default channels, retry policies.
Audit retention: 30 / 90 / 180 / 365 days, plus custom on request.
Integrations: Slack, webhooks.
Danger zone: archive workspace.

What it costs

Alpha organizations default to 4 seats: the owner plus 3 invited teammates. Pilot organizations can be provisioned with a higher seat_limit without changing the tenant model, so a 50-200 person team can roll out inside one organization while teams, workflows, artifacts, and context stay team-scoped.

The current early-partner machine limit is intentionally small. If your first workflow needs additional self-hosted workers, SSO, or custom retention, contact your Viewport operator before routing more team traffic through the workspace.

Create an organization