How user can create project in JIRA without been an administrator ?
Asked by C?line AUDARD:

HI,

In Jira work management, my users can't create new projects exept if they are administrator. Is is possible ? In Global permission, there is no permission to create project, exept team managed projects.

However, when they create new issues (Task, epic ...) they can select many projects already existing in our JIra and so create tickets in any projects, even if they can't see those projects and new tickets. How can I do to block that behaviour and I want that, when a user create an issue in a project, he will be able only to create it in the project where he is at the moment?

Thanks in advance for your help


Answers:
author: Sarah Schmitt-B?r
body: Hi [@C?line AUDARD](/t5/user/viewprofilepage/user-id/4370351) ,

As others have mentioned, creating a new company managed project in Jira typically requires administration permissions. To address this challenge, we've developed an app, called [Templating.app](https://marketplace.atlassian.com/apps/1224664/templating-app-jira-issue-templates-project-templates?hosting=cloud&tab=overview), that empowers administrators to generate project templates using available schemes. Moreover, administrators can specify users and groups permitted to utilize these templates without the need of having administration privileges. This solution could potentially resolve your issue.

I am the Product Manager for this app. So please don't hesitate to contact me if you have any questions ?.

Cheers,

Sarah

![Bildschirm?foto 2024-03-25 um 22.52.06.png](https://community.atlassian.com/t5/image/serverpage/image-id/314312iD922F1ED532EA6D4/image-size/large?v=v2&px=999 "Bildschirm?foto 2024-03-25 um 22.52.06.png")


author: Alex Koxaras _Relational_
body: Hi [@C?line AUDARD](/t5/user/viewprofilepage/user-id/4370351)

Only Jira administrators can create company managed projects. However, as you correctly stated, there is the global permission of granting users the ability to create their own team managed projects. Within the latter projects, and because they don't share any configuration with other projects, users can do peetty much whatever they want, without affecting other projects.

Now onto the second part of your post. Each project is bound to a permission scheme. This scheme defines what uses can do inside a project. These schemes however, in company managed projects, are sharable and can be used by many other company managed projects. Within this permission scheme a user is granted permission such as browse project (to be able to see the project), create issue, edit issue, transition issue, comment issue, edit comment etc.

This set of permissions works per project. But is this scheme is shared with other projects then a user can have access to the other projects as well. This reduces a jira admin workload and maintenance, but could potentially increase "security" issues if the initial setup is done poorly.

I would strongly advise to read:

* <https://support.atlassian.com/jira-cloud-administration/docs/manage-global-permissions/>
* <https://support.atlassian.com/jira-cloud-administration/docs/manage-project-permissions/>
* <https://support.atlassian.com/jira-cloud-administration/docs/permissions-for-company-managed-projects/>
* <https://support.atlassian.com/jira-cloud-administration/docs/manage-project-roles/>

The above documentation will help you understand better how permission work in Jira.

comments: author: C?line AUDARD
body: Hi, I would like to thank you very much as your article help me a lot. Thanks another time, and have a good day


author: Alex Koxaras _Relational_
body: Glad to know that! Kindly mark my answer as accepted to help others in the community to find proper answers! Thanx.


author: Josh Allen
body: Are there any plans to have both Company Managed and Team Managed projects in the Jira Work Management world similar to Jira Software?

We use Jira Software, but I really really want calendars and list view, however, I'm not willing to take the leap to JWM because I want teams to take ownership of creating and administering their projects (team managed) rather than having to administer them with ridiculous amounts of permissions schemes as it is in company managed.


author: Pramodh M
body: Hi [@C?line AUDARD](/t5/user/viewprofilepage/user-id/4370351)

We have to work in bits and pieces here

There's a permission scheme associated with the project. You have browse and create issue permission in the project which is given to roles, and then the user is assigned to a role.

Please go through the documentation of the permission scheme to exactly know about the permissions in Jira

<https://support.atlassian.com/jira-cloud-administration/docs/manage-project-permissions>

Thanks,  
Pramodh

comments: author: C?line AUDARD
body: Hi, Thanks a lot for your answer, I'm going to have a look on that.

Have a good day


Tags: cloud