How do I limit which projects certain users can see?

[Scott everett]

I have a few projects I want one team to see, and some other projects I need a different team to see. I do not want either team to see each other's projects. The default permission scheme enables any new user I add to see all projects.

[Ryan Belmont]

double post, trying to delete.

[Scott everett]

Thnks Ryan, I think I understand what you mean with the "People" portion of a project. I've created a new project which is a new feature we are working on, and one that my editors need not see. So I went to this new project, into "people", and removed "users", leaving only "developers". And moving forward, for every project I create, I will simply have to manually remove "users" from the people administration.

Going to go into the permission schemes to try out your recommendation about project roles related to "Browse Projects".

Thanks again to you and Jobin for the advice. Jira's UI is confusing (to me).

[Ryan Belmont]

When you're administering the "People" portion of a project, make sure you don't have Developers and Users added to the groups on the right side of the screen - these are added to a new project by default and will give access to anybody in the system that's part of either of these groups.

Once you've removed those groups, only the people actively added to a project will be able to browse it/see issues.

Oh, and you need to change your Default Permission Scheme for "Browse Projects." Right now I have ours set up so that only the Administrator group and the Project Roles can see the project issues.

[Jobin Kuruvilla [Adaptavist]]

See http://confluence.atlassian.com/display/JIRA/Managing+Project+Permissions

[Scott everett]

Thanks Jobin, but I am having trouble following the wiki. I have created a user group "editorial", as well as a permission scheme called "editorial" which does not include the ability to browse projects. But the effect is that my users cannot see any projects and lose their dashboard.

[Jobin Kuruvilla [Adaptavist]]

Did you apply the editorial scheme only to your project? For whichever projects you want to restrict the visibility, apply the new scheme that has 'browse' permission available only for selected groups.

[Scott everett]

Also, for the default Jira user group "Users", which is what I have currently been adding new editors to, access to all projects is default. So should if I create a new group called "Editors", I am not clear on what then I need to do to ensure new Jira users I add to this group have a dashboard, and can only view and create tickets against the projects "Bugs" and "featuee requests"

[Scott everett]

I guess I am confused by the permission scheme utility. I am going to start from scratch again. My goal is basic (I think). I have two types of employees, developers and editors. I have two projects, "bugs", and "feature requests", that I want the editors to see and be able to submit tickets to. For developers, I will have a muxh larger set of projects, and thus I believe the native "developer" user role will suffice. But, I am confused whether I should use groups, roles, or permission schemes to enable the access I am describing.