Skip to Content
ConfigurationTeam Management

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 three roles:

RolePermissions
ownerFull access. Can delete the project, manage billing, manage members, and transfer ownership. One owner per project.
editorCan create and edit specifications, run planning and implementation sessions, and manage tickets. Cannot delete the project or transfer ownership.
viewerRead-only access to all project data. Cannot create or modify anything.

ℹ️ The user who creates a project is automatically assigned the owner role.

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. Owners manage members, API keys, quality standards, and billing.

Editor — Developers who use SpecForge daily. They create specs, plan with agents, implement, and review. This is the default role for collaborators you invite.

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

  1. Open your project and go to Settings > Team
  2. Click Invite Member
  3. Enter the email address
  4. Select a role
  5. 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 (editor)
specforge members add alice@example.com
 
# Invite with specific role (editor or viewer)
specforge members add bob@example.com --role viewer

Managing 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 by running specforge invitations in the CLI.

Changing Roles

From the Dashboard

  1. Go to Settings > Team
  2. Find the member in the list
  3. Select a new role from the dropdown
  4. Confirm the change

From the CLI

specforge members role alice@example.com editor

⚠️ Only owners can change member roles. You cannot promote someone to owner — ownership transfer is handled separately through the dashboard.

Removing Members

From the Dashboard

  1. Go to Settings > Team
  2. Click Remove next to the member
  3. Confirm removal

From the CLI

specforge members remove alice@example.com

Removed members lose access immediately. Their prior contributions (sessions, commits, reviews) remain in the project history.

Sharing Operations (CLI)

Team management runs through the specforge members and specforge invitations CLI commands above. These are not agent-callable MCP tools — an agent has no team-management tools in its 17-tool surface. Under the hood the CLI dispatches to the platform sharing operations:

OperationCLI commandDescription
invite_to_projectspecforge members addSend an invitation to a new team member
list_project_membersspecforge members listList all current members and their roles
update_member_rolespecforge members roleChange a member’s role
remove_project_memberspecforge members removeRemove a member from the project
list_invitationsspecforge invitationsView pending invitations
accept_project_invitationspecforge invitations acceptAccept a received invitation
decline_project_invitationspecforge invitations declineDecline 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 + editors. Everyone creates and implements specs. One person (owner) manages quality standards and API keys. Keep it flat.

Growing team (5-15): Owner + editors + viewers. The owner handles configuration changes and membership. 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 an editor on one project and a viewer on another. API keys are per-project, so access is naturally scoped.

See Also

API KeysMCP Tools