Skip to main content
New Idea

Agent / Admin Roles - Create and Edit Separate

Related products:Freshservice
  • July 6, 2025
  • 2 replies
  • 30 views
C
Skilled Expert
Forum|alt.badge.img+10

In any of the Agent or Admin Roles the option to create and edit anything, should not be in one tick box. They should be separated. We have teams that are allowed to create assets and some that are only allowed to edit. However, these are together so the teams that would normally only be allowed to edit assets are now able to create them as well. Where this should only be done by a specific team.

 

This is a problem and makes granting access to teams difficult. Do we give them too much access and hope they do not touch or do not create where they shouldn’t or do we remove their access and make more work for another team that would not normally edit these, only create.

 

Furthermore, we should also be able to drill down in Inventory and only give certain teams access to edit or create certain asset types e.g. Computers and Laptops should only be created by End User Device Coordination and Edited by Tech Support. Services should only be created and edited by Service Architecture. This should be able to be done via the role groups.

    2 replies

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

    Having these split would make granting access to certain features / modules, less of a risk. 

    We have some teams that are allowed to edit but not create and this makes it difficult because we are now having to ask people to not create (but because they can see they can - they do anyways as they forget or no care factor) but we cannot remove the access as part of their role is to keep certain modules up-to-date. 

     

    They shouldn’t be creating as this is a different teams process and requires them to keep track of these so it makes the process tedious and requires more administration work to ensure the data is correct.

     

    Having the ability to only grant edit access or create access, would be VERY beneficial. Is there any chance that this is something that is being looked into? As other ITSM tools have the more granular role permissions and makes it easier for administration.

    Daniel Söderlund
    Top Contributor ⭐
    Forum|alt.badge.img+14

    Having these split would make granting access to certain features / modules, less of a risk. 

    We have some teams that are allowed to edit but not create and this makes it difficult because we are now having to ask people to not create (but because they can see they can - they do anyways as they forget or no care factor) but we cannot remove the access as part of their role is to keep certain modules up-to-date. 

     

    They shouldn’t be creating as this is a different teams process and requires them to keep track of these so it makes the process tedious and requires more administration work to ensure the data is correct.

     

    Having the ability to only grant edit access or create access, would be VERY beneficial. Is there any chance that this is something that is being looked into? As other ITSM tools have the more granular role permissions and makes it easier for administration.

    It’s in the roadmap to split up the access, but having edit/delete/create separate would be good.  

    Synerity | Your Nordic Freshworks Partner | Seamless Support & Solutions | www.synerity.eu
      Terms of UseAccessibility statement