Can't Create Company Managed Projects
Asked by Rick Swiderski:

I created a free Confluence instance for my company. That installation and usage went well. A few weeks later I created a free Jira Work Management instance. I was able to create a project, but I wasn't aware of the difference between team managed and company managed projects. In fact, it didn't give me an option between the two. So, what was created was a team managed project. I had used JIRA before on a self-hosted instance so this didn't seem different. I wanted to tweak the workflow, screens and create a custom field. It let me do all of those things. But, there was no way to associate those things to my project. That's when I realized that when JIRA Work Management was set up it didn't make me a 'full' administrator. I do not have the proper level to perform what seem to be company managed project activities. I've been in the User Management section, and there doesn't seem to be a way to change my permission/access level on JIRA to system admin. I did see a couple other questions in the forum that appeared to have the same problem, but none of them had a solution. Is there anyone out there who has encountered this same issue and been able to rectify it?


Answers:
author: Trudy Claspill
body: Hello [@Rick Swiderski](/t5/user/viewprofilepage/user-id/5279599)

Welcome to the Atlassian community.

If **you** create the instance then by default you have full administrative permissions in the instance. Unless you gave administrative access to others and they subsequently removed your admin access, it is unlikely that have you have lost the access.

Let's make sure that you understand the fundamental difference between Team Managed and Company Managed projects.

Company Managed projects are like the projects you were used to in self-hosted instances. They leverage all the issue, field, workflow, screen, permission schemes that you may have been familiar with if you administered a self-hosted instance.

Team Managed projects are very different. They are intended to be "stand-alone". They don't leverage the system level options for creating custom fields, issue types, screens, workflows, notifications, permissions, and so on. Team Managed projects are designed to allow the users who are Project Admins to implement customizations. The customizations apply locally to only the one Team Managed project. A project admin can customize the workflows, fields, issue types, permissions, and notifications for their project without impacting any other project.

The customization functionality available for Team Managed projects is self-contained under the Project Settings option in the project.

Now, when it comes to creating projects you are able to select from a number of project templates.

Some project templates can be used to create a project as either Team Managed or Company Managed. Some project templates support only one architecture.

Also, it is possible to enable a system level setting to give non-Jira Admins access to create only Team Managed (never Company Managed) projects.

For those that support both architectures you have the opportunity to select which one you want from this screen.

![Screen Shot 2023-07-28 at 7.27.51 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/271948i9B3B122EE74203F3/image-size/large?v=v2&px=999 "Screen Shot 2023-07-28 at 7.27.51 PM.png")

When you click on the **Show more** expander, then you get the field for selecting Team or Company Managed.

![Screen Shot 2023-07-28 at 7.28.01 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/271949i2981EC3F1B8492AA/image-size/large?v=v2&px=999 "Screen Shot 2023-07-28 at 7.28.01 PM.png")

If you did lose your admin access, but the system level setting is enabled to let non-admins create Team Managed projects, then it that situation you would not see the above option even if the template does support both architectures.

Once the project is created you can't switch it from Team to Company or vice versa. If you truly need to use the other type of project, then you have to create a new project of that type and then move the issues from the original project to the new project. That process has some limitations, so you would want to review this document first.

<https://support.atlassian.com/jira-software-cloud/docs/migrate-between-team-managed-and-company-managed-projects/>

You can learn more about the differences between Team and Company Managed projects here:

<https://support.atlassian.com/jira-software-cloud/docs/learn-the-basics-of-team-managed-projects/>

comments: author: Rick Swiderski
body: Thanks for the response. I was able to create a company managed project. I thought that I had tried that when I first noticed the difference between the project types and I don't remember seeing the dropdown to select between the two project types. I probably just missed it. Sorry for the confusion.


author: Fernando Eug?nio da Silva
body: Hey [@Rick Swiderski](/t5/user/viewprofilepage/user-id/5279599) , welcome to the Atlassian Community!

To see who can create Company-Managed projects, do the following:

* Click at 'gear' icon on the right side and select **System** option;
* Go to **Global Permissions**
* The user groups who can create **Company Managed projects** are included on the **Administer Jira** permission. You can add a new grupo at the end of the screen or as a Site Admin you can add yourself for any group presented on the list.

Hope this helps you.

comments: author: Rick Swiderski
body: Thanks for the response. I was able to create the company managed project. My original confusion was caused by the User Management Admin section. My user product access section has three entries, one for JIRA Work Management, one for Confluence and one for JIRA Administration. I can only select User in the JIRA Work Management section. That's why I thought I couldn't create the company managed project. But it was probably me just missing the dropdown in the Project Creation flow. Sorry for the confusion.


Tags: cloud

jira-work-management-cloud