Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How to prevent users from changing project details?



We would like to prevent jira users from changing project details, including the project name and key.

We have 3 user groups, site admins, admins and jira users and we have removed the 'Administer Projects' permissions for all groups other than site-admins, however jira users are still able to change project details including the project name and key, which is highly undesirable. We trust our users, however we don't trust users to change project details by accident.

We've tried various options with global permissions, restricted groups, application access and permission schemes, but there doesn't appear to be a permission to control the ability to disable/restrict users from changing project details

Does anyone have a solution for this issue please, or is it a feature we need to live with and hope users do not accidentally change project details?

Many thanks.

1 answer

1 accepted

0 votes
Answer accepted

Hi Anthony,

When "Editing project Details" Any user with the Administer Jira global permission will have the ability to alter the project settings, and user without the global administer permission should require Project admin to have access to project management settings.


Thanks for your suggestion.

We've since fixed the issue, which relates to the 'type' of user access granted when new users are invited to join Jira Cloud from the invite screen.

When inviting users to join the Cloud instance, there is a choice to select the type of user, including the 'Trusted' user ... this 'Trusted' user type was allocated by default when the invites were sent, giving users greater permissions than we wanted.

We needed to select the 'basic' user type when inviting users, which far limits their permissions and prevents them editing the project details, such as project name and key. We just had to change the user type to 'basic' as opposed 'trusted'.

Works a treat, now!

Like Earl McCutcheon likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events