Teams & Organizations

Collaborate on Virke projects with teams. Organizations provide shared project ownership, role-based access control, and member management.

Quick Start

Create an organization

virke orgs create my-team

Invite a team member

virke orgs invite alice@example.com --role dev

Switch to org context

virke orgs switch my-team

All subsequent commands (virke deploy, virke db, etc.) operate under the organization.

Roles

Role Projects Deploy Settings Members Billing
Viewer Read — — — —
Developer Read/Write Yes — — —
Admin Read/Write Yes Yes Yes Yes

Role descriptions

  • Viewer — Read-only access to projects, deployments, and logs. Cannot deploy or modify settings.
  • Developer — Full access to projects. Can deploy, manage databases, and use all CLI commands. Cannot manage members or billing.
  • Admin — Full access to everything including member management, billing, and organization settings.

CLI Commands

Organizations

virke orgs                      # list your organizations
virke orgs create <name>        # create a new organization
  --slug <slug>                 #   custom URL slug
virke orgs switch <slug>        # set active organization context

Members

virke orgs members [org-slug]   # list members
virke orgs invite <email>       # invite a member
  --role <role>                 #   admin, dev, or viewer (default: dev)
  --org <slug>                  #   target organization

Invitations

virke orgs invitations          # list your pending invitations
virke orgs accept <id>          # accept an invitation
virke orgs decline <id>         # decline an invitation

Organization Context

When you switch to an organization, all CLI commands operate under that org:

virke orgs switch acme-corp

# These now operate under acme-corp
virke init --name shared-api
virke deploy
virke db query "SELECT * FROM users"

To switch back to your personal account:

virke orgs switch personal

Check which context you're in:

virke whoami

Logged in as: alice (alice@example.com)
Organization: acme-corp (Admin)

Dashboard

Organization management is also available in the Dashboard:

  1. Create org: Settings > Organizations > Create
  2. Invite members: Organization Settings > Members > Invite
  3. Manage roles: Click a member to change their role
  4. Transfer project: Project Settings > Transfer to Organization

Project Ownership

Projects belong to either a personal account or an organization.

Transfer a project to an organization

From the Dashboard: Project Settings > Transfer to Organization

Or via CLI:

virke projects transfer my-app --to acme-corp

Shared resources

All organization members (with appropriate roles) can access:

  • Projects and deployments
  • Databases, KV namespaces, and storage buckets
  • Deployment history and logs
  • Custom domains
  • Cron jobs

API Keys

Organizations have their own API keys, separate from personal keys.

# Create an org-scoped API key (for CI/CD)
virke orgs switch acme-corp
# Then generate via Dashboard: Settings > API Keys

Use org API keys in CI/CD pipelines to deploy under the organization context.

Billing

Each organization has its own billing. Resource usage (compute, storage, bandwidth) is tracked per organization.

  • Personal projects bill to your personal account
  • Organization projects bill to the organization
  • Transferring a project moves its billing to the new owner

Further Reading