How to lock down Ability to Create Issues, View or create teams, View Apps, Dashboards and Filters

[JD Lobue]

We are wanting to experiment with working w/ one of our clients in our Jira instance. We have created a role to lock down ability to browse, create, and view company managed JSWs, and have a game plan for team managed JSWs. However, an external user is still able to view filters, create issues, view dashboards, and use all other areas of the top bar (see attached). What is the best way to lock down our instance so that our client can come in and only see the project we are giving them access to and not use the top bar located in attachments?

Thanks.

[Walter Buggenhout]

Hi @JD Lobue and welcome to the Community!

You cannot disable the navigation bar in Jira Cloud. It is the map for anyone with a license to the product to find their way around in the product.

However, all the items can be restricted:

• In the list of projects, a user will only be able to see the list of projects he/see has access to. Creating projects is not possible if the user is not a Jira Administrator (company managed) or not a member of a user group allowed to create team managed projects.
• Creating issues is always linked to project permissions. A user can only create issues in projects where he/she has the create issues permission. If he/she does not have access to do so in any projects, he/she will not be able to create issues.
• Filters gives access to existing filters or to the advanced filters section where users can define their own search criteria. A user will only be able to search for and find issues in projects they have access to. Each saved filter can be restricted, so they are only visible to the users that should see them. Train your users to pay attention to these security settings (permissions for a filter can be found in details, next to the filter's name)
• Dashboards can be secured in the same way as filters. Since it is quite common to build a dashboard for a project, it would be quite normal to let your external users access that project dashboard, but restrict other ones.
• To install new apps, one needs to be an Administrator.
• The teams part is quite open in terms of permissions, that is more or less the only area you can't really restrict.

Hope this helps!