nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

What is the difference in "Any logged in User" and "Application Access - Jira Software"

Greg Bowe_v1si36

I am reviewing our permission scheme. We have some permissions allowing "Any logged in User" and "Application Access - Jira Software", is there a difference.

I'm mostly concerned that "Application Access - Jira Software" may pertain to external connectors or users running API commands using a Token.

Does external access (e.g. API, JIRA CLI, Connectors QTest et. al.) require a specific permission other than "Any Logged in User"?

Accepted answers

Mikael Sandberg

The difference is that any logged in user applies to all users that you have on your Atlassian instance, so it could be your Confluence users, JSM agents, and Jira users. Application access - Jira Software is only for users that have been assigned a JSW license.

For external access there are are couple if different ways, all apps that you get from the marketplace has a dedicated user that is added to the atlassian-addons-project-access project role. For the REST API you are using an API token and the access level needed depends on the endpoint you are using.

All comments

Mikael Sandberg

Greg Bowe_v1si36

Thanks Mikael. Given the follow scenario:

I run an API command using greg.bowe@mydomain.com and an API token. Does that call to the API fall into the "Any Logged in User" category?

Mikael Sandberg

It all depends on the endpoint and what permissions you have, but most of the API endpoints require that you have a JSW license and the right permissions in projects.

Setting Any logged in user in the permission scheme to for example manage sprints would only allow users that have a JSW license to manage sprints, since that is a feature in JSW. But you could for example set any logged in user to browse project create issue so that your Confluence users could create new issues, but they would not be able to do anything else.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud