Best Practice for Project Specific Access

[Ben Weisman]

Hello,

    My clients will each need a project in our internal JIRA system where they can access their tickets in said project. Obviously, I dont want them to have access to see other projects. What is SOP for getting this done? Should I use groups and then add that group to the project?

Thanks.

[Joseph Chung Yin]

@Ben Weisman -

Hi Ben:

It is great assisting you again.  Are you referring to Jira Software project or JSM?

If it is Jira Software project, then you can just use the project's Settings >> People to control who can be allow to access the project by assigning them to the appropriate project roles.  If the user is not associated to the project role assignments, then he/she will not be able to access the project.

If it is JSM, then you can uses the following to control the project visibility in the portal UI (customers) - 

In addition, also use Project settings >> People to setup users with project roles to lockdown project access from the project UI.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

[Ben Weisman]

Thanks @Joseph Chung Yin . Does it make sense to create groups for these people or is that not really necessary?

[Ben Weisman]

This is for Software projects.

[Joseph Chung Yin]

@Ben Weisman -

For groups setup, it will be easier for one to assign the groups to project role as long as the group mgmt (adding/removing users) is being managed properly.

Using group is a good idea, but it is not necessary.

Best, Joseph

[Connor]

Hi Ben, have you taken a look through Atlassian's documentation? 

• Manage project permissions
• Permissions for company-managed projects
• Customize Jira Service Management permissions
• Permissions for your service project and Jira site
• Best Practices: Restricting Projects in Jira