Team Management

Effective collaboration starts with clear roles and permissions. Learn how to manage your team in Release Cadence.

Organization Roles

Organization roles control access across all projects:

Owner

  • Full access to everything
  • Manage billing and subscription
  • Delete the organization
  • Assign and remove any role

Admin

  • Create and manage projects
  • Invite and remove team members
  • Manage organization settings
  • Cannot manage billing or delete organization

Member

  • Create and edit features
  • Create surveys and view responses
  • Post to social media
  • View all projects

Viewer

  • View projects and features
  • View survey responses
  • Cannot create or edit content
  • Read-only access

Project Roles

Project roles provide granular control over specific projects:

Maintainer

  • Full control over the project
  • Manage project settings
  • Add and remove team members
  • Delete the project

Contributor

  • Create and edit features
  • Create surveys
  • Post updates
  • Cannot change project settings

Viewer

  • View project content
  • Read-only access
  • Cannot create or edit

💡 Tip: Organization Owners and Admins automatically have Maintainer access to all projects.

Inviting Team Members

Send an Invitation

  1. Go to Settings → Team Members
  2. Click "Invite Member"
  3. Enter their email address
  4. Select their organization role
  5. Optionally assign to specific projects
  6. Click "Send Invitation"

Invitation Process

  • Invitee receives an email with a link
  • They create an account or sign in
  • They accept the invitation
  • They immediately get access

Pending Invitations

View and manage pending invitations:

  • See who hasn't accepted yet
  • Resend invitation emails
  • Cancel invitations

Managing Team Members

Changing Roles

  1. Go to Settings → Team Members
  2. Find the team member
  3. Click the role dropdown
  4. Select a new role
  5. Confirm the change

Removing Team Members

  1. Go to Settings → Team Members
  2. Find the team member
  3. Click "Remove"
  4. Confirm removal

⚠️ Warning: Removing a team member revokes all their access immediately. They won't be able to view or edit any content.

Project-Specific Access

Adding Members to Projects

  1. Open the project
  2. Go to Project Settings → Members
  3. Click "Add Member"
  4. Select from organization members
  5. Choose their project role
  6. Click "Add"

Removing from Projects

Remove someone from a specific project without removing them from the organization:

  1. Open the project
  2. Go to Project Settings → Members
  3. Find the member
  4. Click "Remove from Project"

Teams (Coming Soon)

Teams allow you to group members and assign them to multiple projects at once:

Use Cases

  • Engineering Team: Access to all technical projects
  • Marketing Team: Access to public-facing content
  • Client Teams: Separate teams for each client (agencies)

Benefits

  • Manage permissions at scale
  • Onboard new members faster
  • Organize by department or function
  • Simplify access control

Collaboration Best Practices

Start with Least Privilege

Give team members the minimum access they need. You can always grant more later.

Review Regularly

Audit team member access quarterly. Remove inactive members and adjust roles as needed.

Document Responsibilities

Make it clear who owns what. Use project descriptions to document team responsibilities.

Activity & Audit Log

Track team activity (available on Pro and Enterprise plans):

  • Who created or edited features
  • Who invited or removed team members
  • Who changed project settings
  • Who posted to social media

Team Size Limits

Team member limits by plan:

  • Basic: 5 team members
  • Pro: 15 team members
  • Enterprise: Unlimited

Need more seats? Upgrade your plan or contact sales for custom pricing.

External Collaborators

Clients

Give clients view-only access to their projects:

  • Invite with Viewer role
  • Assign to specific projects only
  • They can see progress but not edit

Contractors

Give contractors temporary access:

  • Invite with Contributor role
  • Assign to relevant projects
  • Remove when engagement ends

Beta Testers

Beta testers don't need team access:

  • Share public roadmap link
  • They can vote and comment
  • No organization access needed

Tips for Success

  1. Onboard Properly: Show new members around and explain your workflow
  2. Set Expectations: Clarify roles and responsibilities upfront
  3. Communicate: Use comments and mentions to keep everyone informed
  4. Trust Your Team: Give people autonomy to do their work
  5. Review Access: Regularly audit who has access to what