Skip to main content

Team Management Overview

GetWebstack has three concepts you need to keep straight when working with more than one person:

  • Organization — billing boundary, owns the seats and the project quota. Every project belongs to one organization. Created automatically the first time you sign up; create more from the web UI.
  • Member — a user who has joined an organization. Each member has an org-wide role: owner, admin, or member.
  • Team — a group of members inside an organization. A team is granted access to one or more projects, with fine-grained per-project permissions.
Organization (billing, plan, seats)
├── Members          ─── role: owner | admin | member
├── Projects         ─── 1 project = 1 codebase + its environments
└── Teams            ─── named groups of members
    └── grants ────── per-project permissions
                      (read · change gws.json · change secrets · delete)

Roles vs. team permissions​

There are two layers of authorization, and they answer different questions:

LayerWhere it's setWhat it controls
Org role (owner / admin / member)Organization → Members tabWho can manage the organization itself: invite people, create teams, change billing, delete the org.
Team permissions (4 booleans per project)Organization → Teams → team → ProjectsWhat members of that team can do inside a specific project — read, edit gws.json, manage secrets, delete the project.

A user who is member at the org level still gets full access to a project if a team they're on grants it. Conversely, an admin only sees projects their teams have been granted.

The four per-project permissions are the same set used for service tokens — programmatic access from CI or AI agents inherits the same model.

Where things live in the UI​

Open the web app and pick an organization — you'll see four tabs:

  • Members — invite people, change their org role, remove them.
  • Teams — create teams, add members, grant project access.
  • Projects — list of projects in this org; click one for its Secrets, Service Tokens, and config tabs.
  • Billing — plan, seats, payment methods, invoices.

Plan requirements​

ActionPlan needed
Single-user use, one projectStarter (free)
Inviting members, creating teamsBusiness
Larger seat / project countsAdjust seats from the Billing tab

When you try to invite a member on Starter, the UI prompts you to start a free trial of Business.