Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Permission Scheme for external users - best practices

I'm raising this discussion to collect your feedback about a Permission Scheme scenario.

- Default Jira Projects are visible to everyone inside the company.
- Some Projects have proper permission scheme due to security and sensitive information (keep this out of the challenge).

- We need to have the rule to add and remove external users to Jira Projects.

Build a Permission scheme to face a demand need to have several contractors working in JIRA. One contractor should see only the Jira project required and must not see any other Jira project.

This is a challenge to share your knowledge and experience.

I have my solution implemented and I will share here in a few days...
Let the game begin...

1 comment

Daniel Ebers Community Leader Mar 15, 2020

this sounds like a familiar use case that I come across often.

I also know configurations where Jira projects are open for everyone inside the company but not to external staff.

In many cases that I have seen a configuration is used where external staff reporters can see their issues they have raised (utilizing 'Browse Permission').

Additionally on some issues they are put to watchers.

Speaking of project configuration there is always a role for Internal Users and one for External Users. There is also a Members Role.

In case the external user is especially trustworthy he can be put to Members Role for some specific projects. This needs approval by a higher management level (and probably HR, too).

Technically speaking the external staff users are managed by LDAP. They are all in a special "external staff" group. The configuration inside Jira relies on the default settings we crafted. Of course, like described in the beginning of this post, Project Admins are able to fine-tune the permissions for special cases.

Apart from that we assured by reviewing the Permission Schemes that external staff users are not able to promote other external staff users (for example an internal staff member must add another external staff member to watchers if one should be added to the list).
Also some others restrictions are in place, for example the one that external staff members are not allowed to delete comments whereas internal staff members are allowed to do so.
This is more the cherry on the top - it might not be needed in every use case scenario.



Log in or Sign up to comment
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

171 views 6 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you