Team Management

Your team members are the people who build, manage, and support your project behind the scenes. PathPro's team management system lets you invite collaborators, assign roles with specific permissions, and control who can do what across your project.

Inviting Team Members

To add someone to your team, navigate to your project's Settings page and open the Team section. You'll find an invitation form where you enter the person's email address and select the role you want to assign them.

PathPro sends an email invitation to the address you provide. The email contains a unique invitation link that takes the recipient to your project where they can accept the invite. You can send multiple invitations at once — there's no need to wait for one person to accept before inviting the next.

Pending invitations are displayed in the team section so you can track who has been invited and who hasn't accepted yet. If an invitation goes unanswered, you can resend it or revoke it and invite someone else.

Invitation Flow

When a team member clicks the invitation link in their email, the flow depends on whether they already have a PathPro account:

  • Existing PathPro user — If the invitee already has a PathPro account (perhaps they're a community member on another project), they're prompted to log in. After logging in, the invitation is automatically accepted and they're added to your project with their assigned role.
  • New user — If the invitee doesn't have a PathPro account, they're taken to a registration page pre-filled with their email address. After creating an account, the invitation is accepted and they immediately have access to your project.

Each invitation link contains a unique, secure token that expires after a set period. This ensures that invitation links can't be reused or shared with unintended recipients. If a link expires before the invitee accepts, simply resend the invitation to generate a fresh token.

The token-based approach also means that invitations are tied to the specific email address — the invitee must register or log in with the email that received the invitation. This prevents someone from forwarding an invite link and having another person accept it.

STEP 1 STEP 2 STEP 3 Send Invite Email address designer@company.com Role Team Member Send Invitation Email Received You're invited to join Acme SaaS on PathPro Accept Join Project Sarah joined as Team Member Acme SaaS Project
Team invitation flow showing the email invite and acceptance process

Team Roles

PathPro offers three team roles, each with a different level of access and responsibility. Roles are assigned per project, so the same person can be an Admin on one project and a Team Member on another.

  • Admin — Full access to everything in the project. Admins can manage settings, invite and remove team members, create and edit task groups, manage features, publish release notes, handle support tickets, and access analytics. Every project must have at least one Admin (the project creator is automatically the first Admin).
  • Team Lead — Broad access to day-to-day project management. Team Leads can create and manage tasks, respond to community submissions and support tickets, publish release notes, and moderate comments. They cannot modify project settings, manage billing, or invite other team members.
  • Team Member — Focused access for contributors who need to work on tasks and engage with the community. Team Members can update tasks assigned to them, reply to support tickets, post comments, and view community submissions. They cannot create task groups, manage features, or access project settings.

Choosing the right role matters. Give Admin access only to people who need to manage the project's structure and settings. For most collaborators — developers, designers, support staff — the Team Lead or Team Member role provides everything they need without exposing sensitive configuration options.

Managing Team Members

The team section in your project settings shows all current team members and pending invitations. From here, admins can perform several management actions:

  • Change roles — Promote a Team Member to Team Lead, or adjust an Admin down to a different role. Role changes take effect immediately and the team member's permissions update the next time they load any project page.
  • Remove members — Remove a team member from your project. Their account isn't deleted — they simply lose access to this specific project. Any tasks they created or comments they posted remain in the project.
  • Resend invitations — If a pending invitation wasn't received or expired, you can resend it. This generates a new token and sends a fresh email to the same address.
  • Revoke invitations — Cancel a pending invitation before it's accepted. The original invitation link becomes invalid immediately.

When a team member is removed, they can still be re-invited later if needed. Re-inviting follows the same flow as a new invitation — they'll receive an email and need to accept it to regain access. Their previous activity (comments, task updates, etc.) is preserved and attributed to their account.

Free Plan Limitations

Team member support is not included on the free plan. On the free tier, only the account owner (Super Admin) can manage the project — you cannot invite Admins, Team Leads, or Team Members. To add team members to your project, you'll need to upgrade to a paid plan.

If you need collaborators on the free plan, consider whether they can participate as community members instead. Community members can view the roadmap, vote on features, submit feedback, and comment — which covers many collaboration scenarios without requiring a team seat.

When you're ready to bring on team members, upgrading takes effect immediately and unlocks team invitation capabilities so you can start building your team right away. See Billing & Plans for a full comparison of what each plan tier includes.

Use Case Shout-Out
Invite your designer as a Team Member on the marketing project — they can manage tasks and reply to community feedback without full Admin access.