Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

JSM Portal-Only users access to Jira Product Discovery

Rick Austin
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 6, 2026

We use Jira Service Management (JSM) for our customer support portal allowing customer users to search and view documentation in the portion of Confluence exposed through our support site and to submit and track Jira support tickets.

We would like to enable all our customer users to submit ideas for product improvement into Jira Product Discovery (i.e. submit idea, find related ideas, upvote ideas, etc.). Reading up on the topic it's not clear if this is possible or not, to allow portal-only users to access JPD without a license. There is no way we can afford to license all our users for Atlassian for the infrequent case where the user needs to submit an idea.

Is it possible to enable portal-only users for access to JPD and if so, what steps would need to be taken? We are not using an IDP (i.e. SAML or otherwise) for managing user access, users log directly into their individual portal-only accounts. Thanks for any guidance, it would be much appreciated.

4 answers

1 accepted

1 vote
Answer accepted
Tanguy Crusson
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 12, 2026

Hi @Rick Austin , you can find what we support today here

Basically:

  • You can publish a view but you currently can't share it with customers, just Atlassian accounts (we're planning to change that)
  • They can't vote (we're also planning to change that)
  • They can submit feedback via JSM (and then you add the tickets as insights in JPD)

We're currently in the middle of a project to improve all this. 

Rick Austin
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 14, 2026

Thank you @Tanguy Crusson, sounds exciting and looking forward to these future enhancements and would be happy to be an early adopter. Any idea on timeframe when this capability might land?

After doing a lot of further reading it does sound like what we are trying to do is possible, but with constraints. It starts with converting Portal-only users to Atlassian accounts and making sure the users are assigned a specific role so they can only access JPD and stay on free tier (we are not using SSO). Further research seemed to indicate there are some gotchas to navigate but they all sounded possible if we are able to live with the constraints.

Along the lines of...

  1. Set up an isolated JPD project
  2. Migrate a few test users to validate the concept and make sure access controls hold and confirm on billing page. Users migrated to jira-servicemanagement-customers-<workspace-name> with no default product access.
  3. Add users to group we have granted JPD Contributor role and add that group to the JPD project. Assign Contributor role NOT product access (if you do, this would consume a license)
  4. Convert users from Portal-only users to Atlassian accounts
  5. Repeat above in waves

Downside and limitations

  1. Voting on ideas is limited and will probably not work in the way we would like.
  2. Comment attribution breaks (JDSCLOUD-7844)
  3. Need to verify organization membership holds and if not reassign
  4. Customer user now have site access, not just portal access so we have to be super careful we don't accidentally open up access.

Let me know if I am missing something. And please let me know if we can be early adopters of the new capabilities you are working on. Thank you.

Like Sami Shaik likes this
1 vote
Aaron Pavez _ServiceRocket_
Community Champion
August 6, 2026

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

0 votes
Jens Schumacher - Released_so
Community Champion
August 15, 2026

@Rick Austin you might also want to take a look at Released Hub in the Atlassian marketplace.

It already does everything you're asking for and more. 

Here is an example of a portal created with it: https://hub.released.so

0 votes
Sami Shaik
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 9, 2026

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.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events