Skip to main content
New Idea

Default Roles - Ability to Edit

Related products:Freshservice
  • October 21, 2025
  • 4 replies
  • 85 views

Forum|alt.badge.img+10

We should be able to edit the default roles. They are a good start to what kind of access is required for each role BUT we would like the ability to be able to edit those roles to add and remove certain permissions e.g. we do not want all agents to be able to have access to all solutions permissions. This should be separated till after they have done the KCS training and also only certain access should be available to each agent or team. 

 

Because we cannot edit it, we have to hope that no one grants access to the default roles and re-create them with similar names but with only the access we require them to have. There is no way to deactivate them either or re-name them to DO NOT USE.

4 replies

DanielRuff
Top Contributor ⭐
Forum|alt.badge.img+9
  • Top Contributor ⭐
  • October 21, 2025

I'm not entirely sure whether that might cause other issues, such as removing permissions from the Account Admin role and potentially locking yourself out. I definitely agree that dealing with these permissions can be frustrating at times.

We've decided not to use the default roles. Only Account Admin and IT Supervisor are used for administrative access. All other default roles are not in use. Our custom roles are labeled using the format “Company Name – Role Name”.

Hopefully, this will become easier once they finally revamp the permissions as originally planned for Q1 2025, introducing a more granular permission structure.


Forum|alt.badge.img+10
  • Author
  • Skilled Expert
  • October 21, 2025

I mean sure, leave the account admin one but you also, it would be good if you could mark someone as the account admin and then no one can remove their permissions unless someone else takes over the role. That way, there is always someone with god rights and the system is aware that that person is the SME of the system and there is (no matter what) someone who can fix any issues with the account admin permissions. 

The other roles on the other hand, should be editable. Or be able to be deactivated so that they are not visible in the permissions. Otherwise, it makes administration more difficult - as they are also the first ones that show up in the drop down when you are granting permissions. It also means that if anyone moves between the roles of Account Admin, you then have to tell them NOT to use those roles. It is just another thing that makes it more difficult to have people move in and out of the role and more things you would have to explain of do not use that because xyz.


Forum|alt.badge.img+10
  • Author
  • Skilled Expert
  • February 2, 2026

Not having this ability is frustrating. Plus you cannot hide these roles or archive them so they do not show up in the list of access roles. 

 

There are certain functionalities that the default roles give access to that we do not want our agents or supervisors to have access to but we cannot remove it from the default roles. It would be beneficial to be able to edit these as these are the roles that automatically get updated when new permissions are added.


Forum|alt.badge.img+1

The ability to hide, remove, or at minimum sort/filter out-of-the-box roles in the UI would significantly improve administrative efficiency. This becomes especially important in environments actively customizing roles, where clarity and clean UI directly impact security and operational efficiency.

Currently, default roles create confusion, clutter the interface, and force teams to rely on renaming conventions and workarounds instead of clean role management. This increases the risk of misconfiguration and makes it harder to maintain consistent permission models across systems.

Providing visibility controls (hide/archive) or better separation of system vs custom roles would greatly improve usability, governance, and scalability of role management.