If not, you'll need at least one group to assign to our project role later on. If you already have a group or groups set up, you can skip this step. Each group should only be able to access their corresponding project. By using project roles as well as groups to achieve this, we'll only need to use one permission scheme. In our example, we also have 3 groups: Human-Resources, Teams-in-Space, and Technical-Crew. We have three projects: Teams in Space (TIS), Human Resources (HR), and Technical Crew (TC). We're going to use a scenario to demonstrate how this works. See Managing project roles for more information. To configure project role membership within a project, go to the project and choose Project settings > People. To create a new project role, go to Jira settings > System > Project roles. The membership of project roles is defined in the project settings and is valid only for that project. Project roles work like groups, but they're not global.
#CLOUD BROWSE UPDATE#
See Create and update groups for more information. If only users of the group Teams-in-Space should have access to the Teams In Space project, you need to make sure that that group-and no other group-has Browse Projects permission on the permission scheme associated with the project. You can create and manage groups at Jira settings > User management > Groups. Groups are global, meaning that if you're a member of a group like administrators, you're a member of the group for all of Jira. Only site administrators can manage groups. See Managing project permissions for more information. To be able to access a project and view its issues, you need the Browse Projects permission on the permission scheme associated with the project. The permission scheme ( Jira s ettings > Issues > Permission schemes) dictates all the permissions in the projects it's associated with. We'll then use these to restrict access to projects.
#CLOUD BROWSE HOW TO#
Here we'll illustrate how to restrict project access so that each group can only access their corresponding project in Jira Cloud.īefore restricting access, there are three concepts that are important to understand: permission schemes, groups, and project roles.
Since Jira is usually shared by different teams, it's common to have the need to restrict project access. This article applies to company-managed projects.įor team-managed projects, check out (Jira Software) Team-managed project permissions or (Jira Service Management) Overview of permissions in team-managed service projects
0 kommentar(er)
