JSM Portal-Only users access to Jira Product Discovery

Hi @Rick Austin and welcome to the Community.

I can think of two things:

1. An IDEA form and an automation in JSM that will copy the new idea to the JPD space.

2. If the users are internal, you can add them to JPD as a Contributor. Contributor doesnt need a license.

https://www.atlassian.com/software/jira/product-discovery/guides/getting-started/user-roles-permissions

3. If they are external, they need a Free Atlassian account and they can be stakeholders

Stakeholders must create a free Atlassian account to access a published view.

To learn more about roles and permissions, visit our documentation on product access and project roles.

Hope that helps!

Regards

Hi @Rick Austin , welcome, and @Aaron Pavez _ServiceRocket_ has the right map, so let me add the practitioner detail for your exact constraint, because your situation (portal-only customers, no IdP, no budget for licenses) has a clean answer.

The direct answer first: portal-only accounts cannot access JPD, and no configuration changes that. JPD has no customer portal, portal-only identities exist only inside JSM. So "enable portal-only users for JPD" as literally asked is a no, and the goal becomes delivering your requirements without customers ever touching JPD.

The build that does it, with zero new accounts: keep the front door where your customers already are.

1. Add a "Submit a product idea" request type in your JSM portal (fields matching what your product team wants: problem, impact, workaround)
2. An automation rule creates the linked JPD idea when one arrives (or your triage team promotes selectively), keeping JPD as the internal space it is designed to be
3. Demand counting instead of upvotes: when another customer raises the same idea, link the new request to the existing JPD idea and let automation increment a demand field on it. Your team sees "14 customers asked for this" as a number on the idea, which is honestly a stronger prioritisation signal than anonymous votes
4. Close the loop: when the idea ships or is declined, automation comments on all linked JSM requests, so every customer who asked hears the outcome in the portal they already log into

Customers submit, effectively vote, and get updates, all with their existing free portal accounts. Licensing cost for customers: zero.

If customers browsing and voting on the full idea list is truly non-negotiable, then Aaron's stakeholder route is the only path: JPD published views, with each customer creating a free Atlassian account (a separate identity from their portal-only account). That works, but it introduces a second login for every customer, which for infrequent idea-submitters is usually more friction than it is worth, which is why the portal-front-door pattern above tends to win in practice.