Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to prevent users from changing project details? Edited


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
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

326 views 9 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you