Inviting PO to the project

[Maca Mir]

Hi!

I'm working with a new client, whose Tech Lead is going to be out Tech Lead, so he needs access to our workspace. We're willing to pay for his license, but we need to limit his access to the other projects that we have on the workspace. Is that possible? 

[Robert Wen_Cprime_]

Hi Maca!

You didn't specify if this was for a Team-managed project or a Company-managed project.

For a Team-managed project:

Only private Team-managed projects require project administrators to explicitly identify project members and their roles.  So if all projects are private, your PO will have access to the project that is assigned to him/her.

For a Company-managed project:

You want to make sure the Browse Project permissions in the project's permission scheme includes a role you'll set for your PO.  Here's how it will go

1. The Jira administrator can create a special role (e.g. "Product Owners") 

2. The Jira admin can then add that role or default roles (Administrator, Developers, Approvers, Users) to the Browse Project permissions for a permissions scheme.

3. The Jira admin can then associate the permissions scheme to relevant projects.

4. A project admin can add your PO to the project and assign the PO to the role that grants Browse Project permissions.

[Maca Mir]

Hi, Robert! 

Thanks a lot for your answer and time! I was thinking of making use of the different roles... 

I'll try it and let you know if I have troubles doing so :)

[Trudy Claspill]

Hello @Maca Mir 

Do you have Company Managed project, Team Managed projects, or both in your Jira instance?

Which type of project do you want to make visible to the user?

Visibility of Company Managed projects is managed through the Browse Project permission in the Permission Schemes assigned to the project. You would need to ensure review how that permission is allocated in the various projects and adjust it so that the user is not assigned to a group that has that permission for all projects. For the project the user does need to access, you would adjust the permission scheme so that the Browse Project permission is also assigned to a group or role to which that user gets assigned.

If you have Team Managed projects in your environment, visibility of those is controlled by an Access setting in each project. You would have to ensure that those were set to Limited so that only specified user could access those projects.

This topic has been discussed in many posts in the Jira Communities. If you are dealing with only Company Managed projects in your environment, this is a good reference article.

https://community.atlassian.com/t5/New-to-Jira-articles/How-to-give-a-user-read-only-access-to-a-single-project-and/ba-p/1010143

It talks only about Read-only access, but you can extrapolate from there to also give the user the additional permissions they need.

[Maca Mir]

Hi, Trudy, thanks for your answer. 

We work with boht projects, so I'll keep on looking for the appropiate permission. 

Thanks!

[Trudy Claspill]

If you work with both types of projects you may need to modify the default access for both.

For example, often Company Managed projects use Permission Schemes that grant Browse Projects access to Any Logged In User. If you don't want the user to see any Company Managed projects, you may need to modify the Permissions Schemes used in Company Managed projects to ensure the user won't have access.

If you are also using Team Managed projects the Access setting for those may need to be adjusted. As outlined here you may need to change the Access setting from Open to Limited for Team Managed projects that you don't want the user to see.

[Maca Mir]

Trudy, thanks again for your time explaining me all these in such detail. 

I'll pay a look at my project and accesses to be ready to change it.

Thanks!