Permissions

[Martina]

Hello

I do not seem to get it right by putting permissions right in my jira cloud. I'm in charge and then I want my developers to have full access to all projects we have. Then I want the outside clients to enter into some projects. The outside client should only be able to read, create issues and post comments in the projekt.

So far, I have created two groups, developers and customers as well as project roles for these.
I have created a new permission scheme for my projects where i removed someone logged in and set ddit the role of customers and the group developers. Then they embarrass that all developers see all projects and the customer sees only those they are invited to. i just wont to have one permissions scheme to use for all my projekts

Having a problem ... The customer can create projects and I do not want it to be able to do that. What did I do wrong?

[Mohamed Benziane]

No, unfortunately it is not possible you can have only one permission by project.

You have to manage each project with a new permission scheme, they will be likely identical. 

Regards

[Martina]

I want a standard permission that I choose when I create a project. Now I have one that I've created just the way I want it and I choose it when I create a project. 

[Mohamed Benziane]

If you want a default permission scheme to all new project yes it's possible like you have done.

[Mohamed Benziane]

Hello,

I think that you have multiple customer but they only have to get access to their own project (you have customer b, project a, project b but the customer b need to only  have access to project b i'm right ?) so to manage permission you have to:

1- put users and developers into two separate role in each project role of all project you have

2- create a permission scheme for each project, and manage permission as you want.

3- Only admin can create a project, make sure your customers aren't in jira-administrators group in users management option.

Regards

[Martina]

Thanks! I find the error. In the global permission scheme, it was said that anyone could create indepented projects.

Have still managed to have only have one permissions scheme for all my projects. I have the projects a, b, c, d. Developers see all these but customers b, only see project c and customer a only see project b and so on.

[Mohamed Benziane]

You can't do it with one permission scheme you have to get separate permission scheme. Because if you share one permission scheme the customer who have the edit permission will have it in all project that share this permission scheme.

Sorry for my english.

Regards

[Martina]

Can I have two permission schemes on a project?

The customer should be able to do everything a developer can only have that the client does not have access to all projects that the developers have. Developers are my internal and have full access to all projects while the customer can only be invited to the project.

I have created 5 projects. The developers including me see all 5 projects and the customer did not see when it was logged in. When I invited a customer to a project, I only saw that project. So that should work?

[davy]

Hi Martina,

If the customers are able to create projects it means they are somehow also inheriting the Jira admin permissions.
The Jira administration permissions are set in the User Management.

Verify if the group, customers, has the admin box checked in the Application access configuration in the User Management. (https://<instance name>/admin/accessconfig)
Look for the Jira administration section
If the group has the admin box checked,  unchecked, uncheck it

(source: https://confluence.atlassian.com/cloud/manage-application-access-744721629.html)

Best Regards,

[Martina]

Thanks! I find the error. In the global permission scheme, it was said that anyone could create indepented projects.

Have still managed to have only have one permissions scheme for all my projects. I have the projects a, b, c, d. Developers see all these but customers b, only see project c and customer a only see project b and so on.