We want one of our external vendors to use JIRA with us - how can we create a group security profile so that they can only see specific projects?

[Jonas Andersson · Accepted solution]

Yes you can. Create a group, add the users you want access to the project, create a permissions schema that allows them access and make sure that not the rest of the projects on the JIRA instance allows anonymous access, as this would grant them access to. The simplest way to see if some projects can be browsed by anyone is by simply logging out from JIRA and then visit the dashboard. 

[Amy Hall]

Unfortunately I dont think its not that simple 

Our administrators don't want to make all projects restricted - we want users within our company to be able to browse all projects... however, we want our Vendor to only be able to see a select few... 

[Deleted user]

Amy, Noam and Jonas are correct, but let me see if I can clear things up for you.

1. You will need to create a new permission scheme "external vendor permission schema" (or what ever).
2. Modify that schema to add the external users to the permission you want to allow for that project. You could define a user group ("vendors") if you have multiple users. I would recommend this approach as you can always add additional users to the group and everything will be done.
3. Assign that permission schema to the vendor project you want to allow access to. If no other project uses that schema they will not be able to see/access any project but the one you assigned.

Hope this helps.

[Amy Hall]

Awesome, thank you!!

[Michael Nadeau]

Can this be done in JIRA Cloud?

[Noam Dahan]

@Michael Nadeau Yes

[lijuthomas]

Hi,

If permission access is set to access only a specific project, how can the vendor defects be linked to an epic(features that has multiple projects/vendors associated with it)? Any idea?

Thanks!

[noamdah]

Create a new Permission scheme:

1. Choose  > Issues. 
2. Select Permission Schemes
3. Click the 'Add Permission Scheme' link. 
   
   

And add the group of users to the new permission scheme Browse Projects and take them out of the old permission scheme Browse Projects permission.

Now configure the relevant project that you what then to see to the new permission scheme.