Share a public roadmap

Every project starts private. The public page is a separate, curated presentation at /p/your-project-slug. It contains the copy you choose to publish and the selected product features your community can vote on.

Publish the introduction

An owner or admin opens Community → Set up profile. Write a public display name, tagline, description, and optional website address. Choose a slug and explicitly confirm the copy is suitable for public sharing. You can save a draft before publishing.

The project brief, code, vulnerabilities, evidence, internal descriptions, assignees, and team rationale do not appear on this page. A public profile does not change workspace access.

Choose which features to share

Create a feature or improvement in the private roadmap. In Community, choose Share feature and write a separate public title and description. Hyperoru does not copy the internal description into the publication form.

Security work and finding-linked items cannot be published through this flow. A feature's public status follows its roadmap status, while the public copy remains separately controlled. A profile and its feature must both be published before visitors can see the feature.

Features to share selects eligible product work before pagination and orders it by community votes. Security and architecture tasks cannot crowd those features out of the first page. The list includes drafts and withdrawn features so you can curate them without republishing automatically.

Understand voting

Anyone can read a published profile. Voting requires an active, verified personal account. Each account has one vote per feature, and can remove it. Repeated requests do not create extra votes. API tokens cannot vote or submit public ideas.

Voting closes when the feature is done or canceled, when its voting switch is turned off, or when the profile is withdrawn. A person can still remove their own vote on a visible closed feature. Counts come from stored votes; public visitors cannot inspect voter identities.

Votes inform the team's choices. They do not automatically change priorities, release dates, or security decisions.

Follow Plan with community votes to open the private roadmap sorted by Most votes. The same ordering works in its table and board views and respects the project's filters. Equal vote totals follow priority, then work item number. Use Refresh votes to pick up changes while browsing. Previously collected votes remain visible to your team after a feature is withdrawn, without republishing its copy.

Review incoming ideas

If you enable requests, verified users can submit a title and an explanation. Requests are private to the submitting person and the workspace's authorized moderators. Submission has a daily account limit and rate limiting.

Contributors review requests in Community → Ideas from your community. Accepting a request creates a private feature on the roadmap. Publishing it is a separate decision with separate public copy. Declining keeps the request and the team's reason for reference.

Withdraw a profile

Edit the profile and turn off publication. New public requests, votes, and reads stop immediately at the API; an already open browser may retain what it has already received until its next refresh. Public data uses no-store responses, and the page refreshes when revisited or refocused.

Archiving the project or deleting its workspace also withdraws the profile. Restoring a project keeps publication off until an authorized person chooses to publish again.