Can't edit workflows, project permissions, or ask for support even though I am an admin.

[Niall Ripley]

Hi,

I was reading Jira documentation while trying to edit workflows and project permissions. I was wondering why none of the documentation matched with my project settings page, so I presumed I was missing some permissions. Nope, I'm an administrator but can't seem to edit anything. So logged out, logged in, nothing. 

Therefore I tried to send a ticket and this came up.

I'm assuming site admin is different from project administrator, but nowhere could I find out who site admin was. Also, why do you need to be a site admin to send a ticket, that seems ridiculous. Anyway, checked the accounts matched up on my ticket and the project, and they do.

Where do I go from here?

[Lucas Modzelewski _Lumo_ · Accepted solution]

Hi @Niall Ripley , welcome to the Atlassian Community!

In Jira Cloud, there are two types of projects: Company-managed and Team-managed. Check https://support.atlassian.com/jira-software-cloud/docs/learn-the-basics-of-team-managed-projects/ 

Basically: 

• Team-managed projects: Configured by project administrators, with settings specific to each project.
• Company-managed projects: Use shared configurations between multiple projects, requiring global administration. (Data Center / Server use it)

To find out which type of project you're using, check the bottom of the project sidebar or look at the Type column in the project list.

To modify workflows in a Team-managed project, you need Project Admin access (Administrator role in Access settings), check: https://support.atlassian.com/jira-service-management-cloud/docs/workflows-in-classic-and-next-gen-projects/ 

To contact your Jira Administrator, try:

• Try to check if contact is enabled at [YOURSITE].atlassian.net/jira/contact-administrator
• Ask someone in your company who the administrator is.

---

Atlassian’s support policy makes sense - most Jira/Confluence issues can be solved by a Jira Administrator. If every user contacted Atlassian directly for configuration or custom development issues, it would be a support nightmare since Atlassian wouldn’t have insight into each instance’s setup.

Consider that there are potentially multiple 40,000+ user instances - figuring out who is who and who has the authority to approve requests would be chaotic. 😵‍💫 Named contacts on a license likely serve as 'trusted' users to streamline this process (this is probably documented somewhere).

[Niall Ripley]

Thank you for the insight Lucas, appreciate your help.