GRC Choices - unable to edit fully

[Mike Cook3]

Would like to clean up the OOB Choices that do not pertain to our organization, and also edit / complete other fields.  Have the GRC Admin role, but the role seems to be lacking ability in the Policy and Compliance area, (Risk works better).  Our System Administrator says there is an ACL to allow GRC Admin to edit - but he doesn't understand why it's not working.

Not having problem in Dev environment where I have Admin role. Was this intentional?  If so, why?

Any downside to deleting OOB Choices we don't plan on using?  Don't want to have Users have to see a list of 41 non-applicable choices.  Be nice to have a Hide field.

An option (cumbersome) is to submit clean up list to our System Administrator to edit Choice (data) table.

[Ashik3]

Hi Mike,

If you are using UCF, GRC Choices like Type and Category gets populated from UCF. So A complete cleanup wouldn't be a good idea. Please double check if your UCF content updated Type & Category on Policy Statement.

Thanks,
Ashik

[Jorge G_ · Accepted solution]

I would recommend for your Sys Admin to create a new dropdown with only the options that pertain to your organization while keeping the OOB field intact - keeping it as reference may prove useful/helpful in the future. Remove the OOB fields that have nothing to do with your process off the form and just utilize the ones that are relevant. This can be done with the Form Designer which is a simple drag-and-drop interface where you can add/remove fields.