Team Management
Invite collaborators, assign roles, and manage project membership.
SpecForge projects support multiple team members with role-based access. Manage your team from the dashboard or the CLI.
Roles
Every project member has one of four roles:
| Role | Permissions |
|---|---|
| owner | Full access. Can delete the project, manage billing, and transfer ownership. One owner per project. |
| admin | Can manage members, API keys, quality standards, and all specifications. Cannot delete the project or transfer ownership. |
| member | Can create and edit specifications, run planning and implementation sessions, and manage tickets. Cannot manage other members or project settings. |
| viewer | Read-only access to all project data. Cannot create or modify anything. |
ℹ️ The user who creates a project is automatically assigned the
ownerrole.
Choosing the Right Role
Owner — The person responsible for the project. Usually the founder, tech lead, or project manager who decides adoption and configuration. One per project by design.
Admin — Team leads who need to manage quality standards, API keys, and membership. They can configure how strict the gates are, invite new members, and adjust project settings. Give admin to people who need to change how the team works, not just what the team builds.
Member — Developers who use SpecForge daily. They create specs, plan with agents, implement, and review. This is the default role for most team members.
Viewer — Stakeholders who need visibility without edit access. Product managers reviewing progress, executives monitoring dashboards, clients tracking deliverables. They see everything but can’t change anything.
Inviting Team Members
From the Dashboard
- Open your project and go to Settings > Team
- Click Invite Member
- Enter the email address
- Select a role
- Click Send Invitation
The invited user receives an email with a link to accept. They must have a SpecForge account (or create one) to join.
From the CLI
# Invite with default role (member)
specforge members add [email protected]
# Invite with specific role
specforge members add [email protected] --role adminManaging Invitations
Invited users can accept or decline from the dashboard or CLI.
# Accept an invitation
specforge invitations accept <invitation-id>
# Decline an invitation
specforge invitations decline <invitation-id>✅ Find pending invitation IDs by checking your notifications in the SpecForge dashboard, or through the
listMCP tool withtype: invitations.
Changing Roles
From the Dashboard
- Go to Settings > Team
- Find the member in the list
- Select a new role from the dropdown
- Confirm the change
From the CLI
specforge members role [email protected] admin⚠️ Only owners and admins can change member roles. You cannot promote someone to
owner— ownership transfer is handled separately through the dashboard.
Removing Members
From the Dashboard
- Go to Settings > Team
- Click Remove next to the member
- Confirm removal
From the CLI
specforge members remove [email protected]Removed members lose access immediately. Their prior contributions (sessions, commits, reviews) remain in the project history.
MCP Tools for Team Management
The following MCP tools are available for managing teams programmatically:
| Tool | Description |
|---|---|
invite_to_project | Send an invitation to a new team member |
list_project_members | List all current members and their roles |
update_member_role | Change a member’s role |
remove_project_member | Remove a member from the project |
list_invitations | View pending invitations |
accept_project_invitation | Accept a received invitation |
decline_project_invitation | Decline a received invitation |
Practical Patterns
Solo developer starting out: You’re the owner. No team management needed. Create your project, generate your API key, and go.
Small team (2-5): Owner + members. Everyone creates and implements specs. One person (owner) manages quality standards and API keys. Keep it flat.
Growing team (5-15): Owner + 1-2 admins + members + viewers. Admins handle day-to-day configuration changes. Viewers for product managers and stakeholders who monitor progress. Use separate API keys per developer.
Large team with multiple projects: Each project has its own owner and role structure. A developer can be admin on one project and member on another. API keys are per-project, so access is naturally scoped.
See Also
- API Keys — Generate keys for team members
- Quality Standards — Settings that admins can configure