RequestHunt is a community-driven platform that collects and curates feature requests from X (Twitter), Reddit, and GitHub. We help product teams discover what features real users are asking for, making it easier to validate product ideas and prioritize feature development based on actual user demand.

How does RequestHunt collect feature requests?

RequestHunt uses AI-powered extraction to automatically collect feature requests from social media platforms including X, Reddit, and GitHub. The platform monitors discussions, issues, and posts to identify genuine user feature requests, extracting key information like the requested feature, product mentioned, and user sentiment.

Who uses RequestHunt?

RequestHunt is used by product managers, founders, developers, and product teams who want to discover what features real users are requesting. It's particularly valuable for startups looking to validate ideas, established companies prioritizing their roadmap, and developers building products that solve real user problems.

Is RequestHunt free to use?

Yes, browsing and searching feature requests on RequestHunt is completely free. We also offer API access for developers who want to integrate feature request data into their own applications. Check our pricing page for API plan details.

How often is RequestHunt data updated?

RequestHunt continuously collects feature requests from Reddit, X (Twitter), and GitHub. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[Penpot] Implement project-level permission control

Allow different user roles for the same user across different projects within the same team. Currently, permissions are only at the team level.

Original Source

@@tanzhi88 | 0 pts | 5h ago

### Is your feature request related to a problem? Please describe. Currently, Penpot only supports team-level role assignments (Viewer/Editor/Admin/Owner). Once a user is assigned a role in a team, this permission applies uniformly across all projects within that team. ### Describe the solution you'd like. Implement project-level permission overrides, allowing the same user to have different roles in different projects within the same team. # Use Case Example - User A is Editor in Project A (can edit designs) - User A is Viewer in Project B (can only view/comment) - User A has no access to Project C (project invisible to them) | Scenario | Current Workaround | Problem | | --------------------------------------------------------- | -------------------- | ----------------------------------------------------- | | External contractors need edit access to only one project | Create separate t

Discussion

Loading comments...