Granting Contributor Access from Group
Asked by Matt Richards:

We are in the process of setting up Google Workspace as our identity provider for Atlassian. In this way, our Google Workspace users will automatically be created in Atlassian and added to a Group in the Directory. This group is then used to grant access to various Atlassian products.

We would like to use this group to grant contributor access to JPD, but it appears as though the "user" role is the only one available. How do we give the group members contributor access to JPD?

![jpd.png](https://community.atlassian.com/t5/image/serverpage/image-id/271048iF2C07101A5E0BE7E/image-size/large?v=v2&px=999 "jpd.png")


Answers:
author: Tanguy Crusson
body: [@Matt Richards](/t5/user/viewprofilepage/user-id/5202592) we are going to work on a new product access role called "contributor" in the experience you shared above.

For now though, if you want people to be contributors, they either need to have a Jira license (for any Jira product) or be part of the jira-product-discovery-contributors-xyz user group. Soon you'll be able to select another group than this default one.

(I do not personally know how you sync users in a group with Google Workspace though.)

comments: author: Matt Richards
body: Thank you for your response. The Google Workspace side of things can be ignored for the purpose of this issue. Ultimately I just need to be able to grant contributor access to JPD from a group that I create.

Is that not possible at this stage?


author: Tanguy Crusson
body: Hi [@Matt Richards](/t5/user/viewprofilepage/user-id/5202592) it's not possible yet but we do have that on the short term list of things to do


author: Matt Richards
body: Thank you for confirming. We can work around it for now, but ultimately this is important in our view (and I would imagine for larger customers who need to automate provisioning in this way).


author: J?rg von Livonius
body: Hi [@Tanguy Crusson](/t5/user/viewprofilepage/user-id/502312)

we use Atlassian Access in combination with Azure AD to maintain our groups. There is an urgent need to be able to manage JPD contributors in this way.

You said it's on your short term list. Is there a timeline for this feature?


author: Gary Spross
body: It's my understanding that if a user has a Jira license (software, service management, and/or work management), then they are a "Contributor" within JPD by default. They only need to be added (licensed) to JPD if they need to be a "Creator". This will also require a license which will in turn incur a cost for that user.

<https://community.atlassian.com/t5/Jira-Product-Discovery-articles/A-big-update-on-Jira-Product-Discovery-pricing-creators-and/ba-p/2304729>

From the above article...

"

#### Who can be a Creator? {#toc-hId-260760171}

Any user with product access to Jira Product Discovery on the site ("licensed user") can be added as a Creator to a Product Discovery project.

From a billing/licensing perspective any user who is given product access to Jira Product Discovery is considered a Creator, whether they've been added to a Product Discovery project or not.

"

comments: author: Matt Richards
body: Thanks for your response.

Our users have Confluence licenses but not Jira or JPD licenses. I assume we can manually add them to the "jira-product-discovery-contributors-venvee" group to give them contributor access for free as a function of their Confluence license, but perhaps I am wrong?

Assuming I am not, the problem I have is that I can't seem to grant JPD contributor access because when one adds a product to a group and selects JPD, only "user" is available and not "contributor" as shown in the image that I included in my post.


author: Sebastian Pechhold
body: Hey there..

is it possible to assign the contributor group automatically by default?

Goal: Every new sign up from our company on our workspace <https://simplydelivery.atlassian.net/>

should be assigned to this group without any product access.

comments: author: Rohan Swami
body: [@Sebastian Pechhold](/t5/user/viewprofilepage/user-id/4896154) unfortunately we don't support this at the moment. We have an [open feature request](https://jira.atlassian.com/browse/ID-7783) you can upvote and follow, but this isn't on our roadmap at the moment.


author: Rohan Swami
body: [@Matt Richards](/t5/user/viewprofilepage/user-id/5202592) [@J?rg von Livonius](/t5/user/viewprofilepage/user-id/5175407) we've enabled the feature on your sites:

1. On the upper right of the navigation bar, select ![:gear:](https://a.slack-edge.com/production-standard-emoji-assets/14.0/apple-medium/2699-fe0f.png) \> **Products \> Jira Product Discovery \> Access**.
2. Select **Change group** and make your choice.![Screenshot 2023-09-05 at 2.18.32 pm.png](https://community.atlassian.com/t5/image/serverpage/image-id/278877i5775C34B44E5AE23/image-size/large?v=v2&px=999 "Screenshot 2023-09-05 at 2.18.32 pm.png")

comments: author: Matt Richards
body: Thank you, [@Rohan Swami](/t5/user/viewprofilepage/user-id/2842658) !


author: Rohan Swami
body: [@Matt Richards](/t5/user/viewprofilepage/user-id/5202592) [@J?rg von Livonius](/t5/user/viewprofilepage/user-id/5175407) we will shortly be rolling out the capability to select an existing group to be contributors in Jira Product Discovery. Could you share your site URLs so that we can give you early access?

comments: author: J?rg von Livonius
body: Great, thanks for your support. Our site url is: trivium-esolutions.atlassian.net


author: Matt Richards
body: From your other comment it looks as though you have already enabled this for our site. Thank you!