How to restrict "User (agent)" to certain projects only?

[Gabe Cz]

Hi

Any user with user (agent) right has access to all projects. More so, my user with "Customer", and "User (agent)" role not only has access to a "Team-managed software" type of project but it can delete it with 1 click no questions asked. The project mentioned above has one entry under "Project settings" / "Access" and that is its creator and has Administrator role.

"service management" type seems more customizable. Should we use only that kind of project if we want to have strict(er) access to our helpdesk agents?

I'd like to learn more on how to restrict users on the Project level (of any kind), and not the Product level.

Thanks

[Robert DaSilva · Accepted solution]

Hi @Gabe Cz ,

Your challenge sounds like a combination of Team Managed projects, as well as the Permissions associated with them.

The first thing I would recommend changing is the "Project Access" settings for the service management projects you have. It sounds like you only want specific people to be able to review, comment, delete, or transition tickets. In this case, I would say change the project access from "Open" to "Private".

• You can find this setting under the Project's Settings, and then "Internal Access"
• You are also able to add additional project roles here if you choose, which can have more granular permissions than what comes default.

Secondly, I would recommend changing to using primarily Company Managed projects. These allow you to assign a much more granular permission scheme, which lets you specify specific project roles or people who can perform given actions. I recommend Project Roles for a more re-usable permission scheme, but it's up to you.

For more information on Permission Schemes in Company Managed projects, please feel free to review this Atlassian documentation article: https://support.atlassian.com/jira-cloud-administration/docs/manage-project-permissions/

[Gabe Cz]

The "Team-managed service management" one had that option and i could hide it thanks for that. However the "Team-managed software" does not have the "Project access" / Internal access option. One is a service project the other is a software project.

I will ask the creator of the "Software project" if he can change the project to the other so we can hide it. Not sure why he picked it. We know little to nothing about the project types just yet.

Thanks for the help so far and please let me know if there's a way to restrict the software project / team-managed software project to closed in any way.

[Alex Ortiz]

Team-managed software projects have the "same" process access.  It's just called access instead of internal access.  Also, you have 3 options instead of the 2 in a service management project.  The project admin for that software project should be able to toggle the access for that project to private as well and explicitly add users.

And I just want to echo that company-managed projects are the way to go if you want full control of your project permissions.

[Gabe Cz]

Oh....

"To customize user access, such as roles and permissions, upgrade your plan to Standard."

We're waiting for the xyz department or whoever to validate/approve/finalize our payment so we go from free trial / unpaid to a paid 'full' version.

i'm sure after that it'll work, so I think this is solved then :)

thanks again

[Joseph Chung Yin]

@Gabe Cz -

I agreed with what @Robert DaSilva stated.  In our env, we have stopped using Team Managed Typed project setup for compliance reasons.

For Company Managed Typed projects, you can focus on only grant specific agents to your projects with assigning them the "Service Desk Team" project role.  Thus, you can locked down which agents can access which projects.

Hope this also helps.

Best, Joseph Chung Yin