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

Ah yes great question! 

Company Managed Service Space.

Cheers.

@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.

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

Thankyou both @Gor Greyan & @Trudy P Claspill for the replies.

I will review these documents :)

Another option to explore is Team Managed projects. In those users in the Administrator can manage everything.

Team Managed projects don't leverage the sharable schemes used by company managed projects. However that means the can't share configurations with other projects. Customizations are project scoped. This can cause challenges if your company needs cross team reporting or project configuration governance 

If you aren't familiar with these approach with caution. You would be giving the project admins a fiefdom within your Jira kingdom and what they do in it can impact the rest of the system.

Thanks @Trudy P Claspill  - Unfortunate these Company Managed Service Spaces are already setup and have been used for over a year now... They were also all setup prior to me starting with this company.

I have had a look at this specific project, the Permission Scheme is only used in one Space, not shared. In active Workflows for this project, they are only used in the one space. Nothing is shared.

But yet 'admins' cannot edit Workflows.. The Admin space role is also assigned to 'Edit Workflows' 

Any further advice on this one? Thank you!

Hello @Joshua Stokes 

Didn't you say these are Service spaces?

Per the document link I provided this feature is not supported for Service spaces.

Sorry, yes they are Service Spaces... typo which I have fixed up.

Thanks @Trudy P Claspill