Community Members

Community members are the people who use your product and care enough to participate in shaping its future. PathPro makes it easy for them to join your project, vote on features, submit feedback, and engage with your team — all without any manual invitation process.

How Community Members Join

Community members join your project organically by registering through your project's public pages. When someone visits your roadmap, feature voting page, or any other public-facing section of your project, they'll see a "Sign Up" option in the header. Clicking it takes them through a quick registration form where they provide their name, email, and a password.

Once registered, they're automatically added to your project as a community member. There's no approval step required by default — anyone who signs up can immediately start participating. This frictionless process is intentional: the easier it is to join, the more feedback you'll collect and the larger your engaged community will grow.

If your project is set to Private, the registration page is still accessible, but new community members won't be able to view project content until an admin approves their access. This gives you control over who participates while still allowing self-service registration.

Social Login

PathPro supports social login through Google and Facebook, removing the friction of creating yet another username and password. When enabled, community members see "Sign in with Google" and "Sign in with Facebook" buttons on the login and registration pages.

Social login works seamlessly with PathPro's existing account system. If a community member registers with their Google account, their name and email are pulled from their Google profile automatically. If they later try to log in with their email and password, PathPro recognizes the matching email and links the accounts together.

For project admins, social login typically increases registration conversion rates because it reduces the signup process to a single click. Community members don't need to remember another password, and the perceived trust of using their existing Google or Facebook credentials makes them more likely to complete the registration.

Member Profiles

Every community member has a profile that includes their username, avatar, and optional biography. The username is displayed alongside their votes, comments, and submissions throughout the project, giving them a recognizable identity in your community.

Avatars can be uploaded directly or are pulled automatically from the community member's social login provider. If no avatar is set, PathPro generates a default avatar using the member's initials. The biography field gives community members a chance to describe themselves — who they are, how they use your product, or what they're most interested in.

Profiles help your team put faces and context to the feedback you receive. When you see that a particular community member has voted on several related features and submitted detailed feedback, their profile helps you understand who they are and how they interact with your product.

Community Growth

PathPro tracks your community's growth over time. From the admin dashboard, you can see how many community members have registered, when they joined, and how active they are. This data helps you understand whether your public roadmap and feature voting pages are effectively attracting and retaining users.

Growth tends to correlate with key moments: launching a public roadmap, sharing a feature voting link on social media, or publishing a release note that gets picked up by your users. By watching registration trends, you can identify which outreach efforts are most effective and double down on them.

Tracking engagement metrics alongside raw registration numbers is equally important. A community of 500 members where 200 actively vote is far more valuable than 5,000 registrations with minimal participation. Use PathPro's community data to focus on engagement quality, not just quantity.

What Community Members Can Do

Community members have a focused set of capabilities designed to maximize their ability to give you useful feedback without overwhelming them with admin complexity:

• Vote on features — Browse the feature voting page and upvote the features they care about most. Each member gets one vote per feature, ensuring fair representation.
• Submit feedback — Use the community submissions form to suggest new features, report issues, or share general ideas. Submissions go directly to your admin review queue.
• Comment on tasks and features — Add comments to public tasks and feature requests, participate in threaded discussions, and upvote other community members' comments.
• Create support tickets — If support tickets are enabled, community members can open tickets to report bugs or ask questions, and track the status of their issues over time.
• View the roadmap — Browse your public roadmap to see what's planned, what's in progress, and what's been completed.
• Read release notes — Stay up to date with the latest changes and improvements through your published release notes.

Community members cannot access admin settings, manage tasks, invite team members, or modify project configuration. This separation keeps the experience clean and focused on participation.

Exporting Member Data

PathPro allows admins to export their community member data for use in external tools, newsletters, or analytics platforms. From the admin dashboard's community section, you can generate a CSV export that includes each member's name, email, registration date, and activity summary.

Exports are useful for a variety of workflows. You might import the data into your email marketing tool to send product updates to engaged users, or analyze registration trends in a spreadsheet to plan community growth initiatives. The export always reflects the current state of your community at the time of download.

Privacy matters, so PathPro only includes data that members provided during registration. If you plan to use exported data for marketing purposes, make sure your project's terms of service and privacy policy cover that use case. Being transparent about how you use community data builds long-term trust.