Companies and roles
Company registration
Anyone with a GitHub account and a verified email can register a company. It is active immediately. Whoever registers it becomes its first admin. A company can never be left without an admin.
Company roles
| Role | Does |
|---|---|
| Company admin | Members, invitations, GitHub and settings |
| Product Owner | Vision, priorities, approves specs and releases |
| Project manager | Backlog, assignments, approves specs |
| Tech lead | Architecture, repos, harness, risky actions |
| Developer | Picks tasks and works with their agent |
| Reviewer | Reviews pull requests |
| QA | Validates on staging |
| Observer | Only sees progress (for example, the end customer) |
Project roles
Each person has a company role and, optionally, a different role in a specific project. A developer can be the tech lead of one project without being it in the others.
Current permissions
| Action | Roles |
|---|---|
| Manage the company (members, invitations, GitHub, audit log) | Admin |
| Create projects | Admin, Product Owner, Tech lead |
| Adjust roles within a project | Admin, Product Owner, Tech lead |
| Connect repos and protect branches | Admin, Tech lead |
| See the company and its projects | Every member |
Invitations
With Pro, administrators invite team members by email. Invitations include a role and expire after 7 days. The link can also be copied and shared.
Isolation
Anyone who does not belong to a company gets not found everywhere: they cannot even tell it exists.
External milestone customer
The editor can designate a customer by email without inviting them to join the organization. With their verified email and private link, customers can review scope and decide on their delivery. Use the public link of an approved version to share a read-only sheet.