Plans permission seetings for external users

Stefan Kobitsch-Meyer
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 6, 2024

I would like to give access to Plans (just viewing) on one specific project for one external user. 

What do I need to set on the permissions for this user?

Is it required to create a group first for this one user to set permission on this person? 

Is it required to put this external user to the User Management User List of my company? 

Important is also that this user is not allowed to see other plans or to see other projects, just for the specific project only. 

 

 

1 answer

0 votes
Walter Buggenhout
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
September 6, 2024

Hi @Stefan Kobitsch-Meyer and welcome to the Community!

If the permissions across your site have been configured properly, granting access to an external user is exactly the same as to an internal user:

  • The user needs product access, as viewing data from a Jira project (even through a Plan) requires a license.
  • The user needs browse project permission to the project as well.

Granting this permission is different in company managed and team managed projects, but you grant it in exactly the same way as you would for your internal users.

Coming back to the proper configuration of permissions from my first sentence: making sure that a user does not have access to any other projects than the one you specifically want to allow, obviously may have an impact on any project in your instance.

If you (or your organization) has a practice to grant browse project permissions to any logged in user, then this will expose all these projects to the new, external user as well as soon as he gets his Jira license and logs into your environment. This is something you will need to review across your site.

In practice, that means reviewing all Permission Schemes you have in use for company managed projects and replacing the all logged in users by a user group/project role that only contains your internal users. For team managed projects you would need to verify the permission settings for each project, making sure they are not publicly accessible.

Hope this helps!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events