You subscribe to prev, generate an API key, and hand it to your developers. They can deploy previews, destroy them, and check environment status from the CLI. But when they log into the Dashboard, they see nothing. No deployment history. No logs. No feedback inbox. The API key works, but they're locked out of every visual tool that makes prev useful beyond the terminal.
For solo developers, that's fine. For agencies and teams, it's a dealbreaker. Your project leads need to see what's running. Your designers need to review previews. Your clients need read-only access to the environments you've shared. And until now, none of that was possible without sharing a single account.
Today, that changes. We're introducing Organizations with role-based access control — a first-class way to manage teams, permissions, and shared environments inside prev.
What's New
Organizations are a new layer in prev that sits between individual accounts and your preview environments. When you create an organization, every environment deployed under that org is visible to all members — scoped by their role.
This is a Business plan feature. If you're on the Business plan today, you already have access. Head to Dashboard → Organization to get started.
Here's what's included:
- Create an organization and invite team members by email or shareable link
- Assign one of four roles: Owner, Admin, Developer, or Viewer
- All org members see shared environments, history, feedback, and logs
- Each member gets their own org-scoped API key for CLI deployments
- Switch between your personal account and org contexts in the Dashboard header
Four Roles, Clear Boundaries
Not everyone on your team needs the same level of access. prev's role system gives you granular control without unnecessary complexity.
Owner
The person who created the organization. Owners have full control over billing, membership, and all environments. Every org has exactly one Owner — typically the agency founder or team lead who manages the prev subscription.
Admin
Admins can do everything except manage billing and delete the organization. They're ideal for project leads and senior developers who need to invite teammates, manage API keys, and oversee deployments without touching the payment details.
Developer
Developers can deploy, destroy, and manage preview environments. They can view logs, history, and feedback. They cannot invite new members or manage API keys for others. This is the role for most engineers on your team.
Viewer
Viewers have read-only access to everything: environments, logs, history, and feedback. They cannot deploy, destroy, or modify anything. This role is perfect for client stakeholders, designers reviewing work, or managers who need visibility without the risk of accidental changes.
How It Works
Setting up an organization takes about two minutes.
Step 1: Subscribe to the Business plan. Organizations are a Business plan feature. If you're already on Business, skip ahead.
Step 2: Create your organization. Go to Dashboard → Organization → Create. Give it a name — your agency name, your team name, whatever makes sense.
Step 3: Invite your team. Click Invite Members and enter their email addresses. You can also generate a shareable invite link for larger teams. Choose the role for each invite — you can always change it later.
Step 4: Members join and start working. Invitees receive an email with a link to join. If they don't have a prev account yet, they'll create one during the join flow. Once they're in, they see all shared environments in their Dashboard.
Each member automatically gets an org-scoped API key. Deployments made with that key are owned by the organization, visible to all members:
# Deploy as part of your organization
prev --api-key org_gv60gskk9fvso4ym --subdomain client-portal .The environment shows up in the org's Dashboard for everyone — not just the person who deployed it.
The Org-Switcher
Developers often wear multiple hats. You might have your own Individual plan for side projects and be a member of two different agency organizations. prev handles this natively.
In the Dashboard header, you'll see a context switcher that lets you flip between your personal account and any organization you belong to. Each context has its own environments, history, feedback, and API keys.
Your personal API key deploys to your personal account. Your org API key deploys to the org. They never mix.
# Personal project — uses your individual API key
prev --api-key your_personal_key --subdomain my-side-project .
# Agency project — uses the org API key
prev --api-key org_gv60gskk9fvso4ym --subdomain client-redesign .The CLI doesn't need to know about organizations at all. The API key determines the context. Simple.
Permission Matrix
Here's a complete breakdown of what each role can do:
| Action | Owner | Admin | Developer | Viewer |
|---|---|---|---|---|
| Deploy environments | Yes | Yes | Yes | No |
| Destroy environments | Yes | Yes | Yes | No |
| View environments & logs | Yes | Yes | Yes | Yes |
| View history & feedback | Yes | Yes | Yes | Yes |
| Redeploy from history | Yes | Yes | Yes | No |
| Invite members | Yes | Yes | No | No |
| Remove members | Yes | Yes | No | No |
| Manage API keys | Yes | Yes | No | No |
| Manage billing | Yes | No | No | No |
| Delete organization | Yes | No | No | No |
What's Next
Organizations and roles are just the foundation. We're already working on the next layer of team management features.
SSO (SAML & OIDC) is coming for enterprise customers. If your agency uses Okta, Azure AD, or Google Workspace for identity, you'll be able to enforce single sign-on for your prev organization. Members will authenticate through your identity provider, and provisioning will happen automatically — no manual invites needed.
We're also exploring audit logs, so Owners and Admins can see a timeline of who deployed what, who destroyed what, and who changed which settings. Accountability matters when multiple people share the same infrastructure.
Ready to Bring Your Team On Board?
If you're already on the Business plan, organizations are live right now. Go to Dashboard → Organization and create yours.
If you're on the Individual plan and your team has outgrown a single API key, upgrading takes 30 seconds. Head to Pricing, switch to Business, and start inviting your team immediately.
# Your team is one deploy away
prev --api-key org_your_team_key --subdomain next-big-thing .Full documentation is available in the Team Management guide. If you have questions, reach out at hello@prev.sh — we'd love to hear how your team uses organizations.