Team Management

Overview

Organizations group users under a shared Business account. Each organization has members assigned to roles that control what they can see and do. Team management is available exclusively on the Business plan.

With organizations you can:

• Share preview environments across your team
• Control access with role-based permissions
• Invite members via email or shareable link
• Manage API keys at the organization level
• View audit logs for org-wide activity

Organizations

An organization is created automatically when you subscribe to the Business plan. The user who subscribes becomes the Owner.

Each organization has:

• A name (editable by Owner and Admin)
• A list of members with assigned roles
• Shared environments, API keys, and deployment history

You can switch between your personal account and any organizations you belong to using the Org-Switcher in the dashboard header.

Roles

Each member of an organization is assigned one of four roles. Permissions are cumulative from Viewer up to Owner.

Inviting Members

Owners and Admins can invite new members from the /dashboard/team page.

Steps

1. Navigate to Dashboard > Team
2. Click Invite Member
3. Enter the invitee's email address
4. Select a role (Viewer, Developer, Admin)
5. Optionally send an email notification
6. Click Send Invite

The invitation generates a unique link that is valid for 7 days. If the link expires, you can resend the invitation from the team page.

https://app.prev.sh/invite/abc123def456

Pending invitations are listed on the team page with options to resend or revoke them.

Accepting Invitations

When someone receives an invitation link:

1. Open the /invite/:token link in a browser
2. If not logged in, they are prompted to log in or create an account
3. After authentication, they are automatically added to the organization with the assigned role
4. The Org-Switcher updates to show the new organization

No existing subscription is required to accept an invitation. The invitee uses the organization's Business plan quota.

Switching Context

The Org-Switcher dropdown in the dashboard header lets you switch between:

• Personal Account — Your individual environments, API keys, and history
• Organization — Shared environments, API keys, and history for the selected org

The active context affects all dashboard views. When you select an organization:

• The environment list shows org-wide environments
• Deployment history shows org-wide history
• API keys shows keys belonging to the organization
• Team management is accessible (if you have permission)

Leaving an Organization

Any member except the Owner can leave an organization:

1. Navigate to Dashboard > Team
2. Click Leave Organization
3. Confirm the action

After leaving, you lose access to all organization resources. Any API keys you created within the org context remain with the organization.

Owners cannot leave. To step down, the Owner must first transfer ownership to another member, then leave.

API Keys in Org Context

API keys created while in an organization context belong to that organization, not to the individual user.

• Keys are visible to all members with the appropriate role (Developer and above)
• Admins and Owners can manage all org API keys
• Developers can only manage keys they created
• Labels help identify which team member or service uses each key

# Use an org API key with the CLI
prev create . --api-key <org-api-key>

Environments deployed with an org API key appear in the organization's environment list and history.

Audit Logs

When viewing the dashboard in an organization context, audit logs show org-wide actions including:

• Environment creation and destruction
• Member invitations, joins, and removals
• Role changes
• API key creation and deletion
• Organization settings changes
• Billing events

Each log entry includes the acting user, timestamp, and action details. Audit logs are accessible to Admins and Owners.