Restrict access to a project and all associated issues

[Neil Zaccari]

Is there a way to restrict access to all issues within a project so that only authorized team members can see the issues and contents?

[Neil Zaccari]

It's a small team project that works on issues that contain sensitive information. I want to restrict access to all issues that the team works on.

I did read this

Restricting access to an issue
When creating (or editing) an issue, you can restrict access to that issue to members of your team who are part of a chosen security level. To be able to set the security level for an issue, your administrator must add you to the appropriate issue security level, and also grant you the 'Set Issue Security' permission for the appropriate projects.

How secure is this? Can you tell me more?

Neil

[Max Foerster - K15t]

Just for clarification, do you want to restrict the whole project as you described initially, or do you want to restrict access on a per-issue basis?

If the latter, then I recommend reading the following article:

• Configure issue security schemes 

Can you still please answer my question about what project type you are using and whether you are on the free or standard plan? 

Best, Max

[Neil Zaccari]

Max

I want to restrict access to the project AND the issues inside it. Only the team can see inside the project and at the individual issues

Neil

[Max Foerster - K15t]

Hey, so please stick to the documentation I posted before to restrict and control access to either type of project. After you set that up, you can still think about further restricting access if it's necessary.

[Neil Zaccari]

Max,

I need to get in front of our risk team, I need to know what additional levels of security I can enable so that I can have a complete discussion with them

[Max Foerster - K15t]

It's all here in the thread already. Read through the docs, and you will understand the available options you have within Jira, assuming you choose company-managed projects, to:

• restrict access to projects (project permissions).
• narrow down access for individual issues (issue level security).

Or do you have more specific questions at this point? :)

Best, Max

[Max Foerster - K15t]

Hey @Neil Zaccari, welcome to the community!

Can you tell us what type of project you are using? There's a difference between team-management and company-managed projects. You can identify the type of project in the project's sidebar

For company-management projects, please have a look at the Browse Projects permission. There are a few other things to keep in mind when it comes to managing project permissions, so I leave some links to the documentation here:

• Manage project permissions 
• Permissions for company-managed projects

For team-managed projects, you have to look at the roles:

• Add people to team-managed projects 
• Manage how people access your team-managed project 

That should enable you to configure both kinds of projects according to your needs. :)

Best, Max