Role Permissions for Groups and Organizations

I completely agree with Shannon on this one. We have a few senior staff members who need access to edit organization fields, but they should not be able to create or delete organizations. I set up a security role for "Team Lead" that would allow higher access for these key staff members, but I was disappointed to find that I am unable to designate some of the more granular security privileges that our organization needs. 

+1. We have users who need to be able to manage the groups other users belong to, but they absolutely don't need the ability to delete or create entire groups. 

+1. The level of control around editing, deleting tickets, adding tags etc. should be available for users and organisations too - it's far too easy and destructive for agents to delete users instead of simply suspending them.

+1! We have over 150 agents utilizing Zendesk and this is leaving to much room for error.

Agree! I upvoted this one.

Agreed and upvoted!

Also agree that there need to be more granular permissions for organizations, similar to the permission options available for users.

We also noticed that when a user does not have the permission (add or modify groups & organizations) they aren't even able to see the list of organizations on the "People" admin page. But they could search for and open an organization's page. Just can't see a list of all the organizations...

I've just discovered that there is a lack of distinction between organisation and group permissions. Enabling agent permissions to manage an organisation (which we would like to do) also enables their ability to modify the groups that they, or any other user is a member of - potentially opening a huge privacy issue/window.

I'm actually gobsmacked that there isn't a difference in the way that Zendesk manages these two types of permissions!

+1000. It makes no sense for all reasons listed above

This is just one of many areas Zendesk needs to improve when it comes to Permissions. There are many posts throughout the Community stating there need to be separate permissions for this and that.

A much more gradual permission settings feature is desperately needed. I'm having to make way too many people Administrators to do a single task which unlocks a larger subset of administrative features in Zendesk I don't want that person to access.