---
sourceDocument: Xanadu ServiceNow AI Platform Administration
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/platform-administration

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Choice list security

# Choice list security {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

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

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.

To be able to create new choices for a particular field, an ACL that grants personalize_choices
access for that field is required. For example, to give the hris_admin role the ability to
personalize only the Category field for Human Resources KB articles, you need an ACL granting
personalize_choices access to the hris_admin role on the Category field of the Knowledge
(kb_knowledge) table.

There are predefined ACLs granting both types of access to the personalize_choices security
role, for all fields on all tables. The personalize_choices security role also has read, write,
and delete access to the sys_choices table. However, this additional access is not required when
making just the Personalize Choices functionality available on a granular basis.