Configure choices option on a field but not allow create/add option

[BehelC]

We have a requirement to allow certain users to configure a choice list on the incident form BUT we do not want to allow those users to create new choices. Basically we just want them to be able to right click on the field and activate/deactivate the choices based on current needs. Adding a personalize_choices ACL gives them the ability to create new fields.

This ServiceNow Doc seems to indicate that there is another way to allow a user to select configure_choices on the form on a right click but not having the ability to add new choices for that field. But its kinda confusing and doesn't really specify how to differentiate the two. Then it goes into the ACL part that I already grasp. I've tried adjusting all kinds of ACLs at this point but the personalize_choices ACL type seems to override them all.

So basically we want users with a certain role to be able to get to this page but not see the enter new item section. 

We've also thought about using a table to reference but this would be much easier and less of a learning curve for our users. 

[Aman Kumar S]

Hey,

The SN doc that you have shared, it already says, it doesn't allow creation if you create "personalize_choices" ACL only for the specific field or whole table, user should only be able to move choices as shown in slushbucket and not create new ones.

However, access to the personalize_choices operation on a particular field does not confer the ability to add new choices for that field.

Feel free to mark correct, If I answered your query.

Will be helpful for future visitors looking for similar questions 🙂

[BehelC]

Yes but it also states that if you create a personalized_choices ACL it will give them create access. Which seems contradictory. I was wondering if maybe they were talking about a role vs the ACL but I tried both. I created an personalized_choices ACL and it allowed the user to create. Then I just gave them the personalized_choices role and they were still able to create. Unless I am just misunderstanding something and not doing it the correct way.

[Aman Kumar S]

Its quite confusing to be honest, but the understanding that I got here,

Role:

Use the personalize_choices security role to enable non-administrators modify Choice elements options on all tables.

ACL:

If more granular control is desired, you can also create a custom ACL (security rule) governing the personalize_choices operation either for a particular field or for all fields (.*) on a particular table. However, access to the personalize_choices operation on a particular field does not confer the ability to add new choices for that field.

I think there are some gaps in the documentations, but what I could read, personalize_choices  ACL will provide you access to modify but not create, personalize_choices  role will give you complete access