Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Read much, but still confused on permission control

Ken Brough February 18, 2018

I've just started using Jira. I am Company A with a few projects, and collaborating on 1 specific project with Company B. I want to define a project to which all Company A people have the normal default access that was in place when I created the instance (Default Software permission Scheme) and company B folks can only see their single project, and can only create, view, and update issues.

I have copied the default s/w scheme twice to create schemes A & B. I also created a separate group for company B people.  I then added this group to the needed permissions in scheme B.

Now, "Any logged in User" is still listed in many places throughout schemes A & B. I assume I need to delete this everywhere, create another group for all Company A people and use that instead of "any logged in user" in both schemes?

 Internal only projects get assigned scheme A, the collaborative one uses scheme B.

Does this actually achieve what I want, and Is it the best approach or should I be doing this differently?

Thanks,

Ken

 

1 answer

1 accepted

0 votes
Answer accepted
Craig Castle-Mead
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 18, 2018

Hey Ken,

Assuming I've read/understood your post and requirements correctly, yes - your suggested approach is the way forward.

  1. Given there's 2 different sets of users (companies) in your instance, you're unlikely to want any users to get access in your default permission scheme anymore, so remove all permissions for "All logged in users", actually, remove anything except the administrators group (likely jira-administrators). We've done this in our environment, if a project is created but the permission scheme not changed, the default is users cannot see it.
  2. Create a permission scheme for Company A, and one for Company B (using the relevant groups as a base). Suggest doing this in the permission scheme, rather than via Roles as when you add more projects for Company A or B, you want the permissions to be consistent.
  3. You may want to consider a "blended" permission scheme if/when company A and B have projects they both want to work collaboratively on.

Let us know how you go with that and if you've got any other questions.


CCM

Ken Brough February 21, 2018

Thank you.  Good to know I'm on the right track.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events