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.
Hi @Rick Austin , you can find what we support today here
Basically:
We're currently in the middle of a project to improve all this.
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...
Downside and limitations
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.