nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Setting up a 'SME User Access' account in Jira Cloud

Joshua Stokes

Hello everyone,

I am working with some users in our company that have prior Jira experience and would like more control over there Project/Space, so there is less of a reliance on IT. (Company Managed Service Space)

These users have the below licenses -

- Jira Premium
- JSM/Agent.

The users are also Admin, Service Desk Customers & Service Desk Team within the project itself.

First off, if they are part of all 3 of the above within the project, does this cancel some permissions out? Or does administrator overrule them all?

If it is OK having the user in those 3 groups, what else needs to be updated so they can manage -

- Workflows
- Request Types
- Forms
- Work item types

Within their own Project/Space.

Appreciate the support and guidance in advance, please no AI replies... I would like 'real world knowledge'... I can type into AI myself if needed.

Thank you.

Accepted answers

All comments

Gor Greyan

Hi @Joshua Stokes

One question: are these company-managed or team-managed projects?

That makes quite a difference, because in company-managed projects some configurations (such as workflows, screens, field configurations, permission schemes) may still require a Jira Administrator if they're shared across multiple projects.

Joshua Stokes

Ah yes great question!

Company Managed Service Space.

Cheers.

Gor Greyan

@Joshua Stokes

Thanks for confirming that.

In that case, the users can manage many project-level settings, such as request types, forms, queues, SLAs, customer notifications, and project automation, as long as they have the appropriate project permissions.

For workflows, there's a bit more to consider. Atlassian introduced an Edit Workflows project permission, which allows non-admins to edit workflows only if the workflow isn't shared with any other project or workflow scheme. If the workflow is shared, a user must have the Jira Administrator global permission to edit it.

You can find the details in Atlassian's KB.
https://support.atlassian.com/jira/kb/use-the-edit-workflows-permission-in-company-managed-projects-in-jira-cloud

For other configuration items, such as permission schemes, notification schemes, screen schemes, and field configuration schemes, these are still administered by a Jira Administrator in company-managed projects.

Trudy P Claspill

Note that the Edit Workflows option is not available for Service spaces:

https://support.atlassian.com/jira-cloud-administration/docs/permissions-for-company-managed-projects/#Edit-workflows

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

space

administration

permissions