- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2017 08:47 AM
While doing some research on the current buildout we have I discovered that our users can edit the columns that show up on a list to include ones that are not typically displayed to them on the incident because of our UI Policies. When these columns display their value they can also be edited via the List Editor by double-clicking on it and the changes are saved. Is there a simple way to restrict their ability to modify these fields (I'm not worried that they can see them by changing the visible columns) or do I need to create ACLs for each of the column?
Solved! Go to Solution.
- Labels:
-
Incident Management

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2017 08:48 AM
you can create a ACL list_edit operation type for those fields
Harish

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2017 08:48 AM
you can create a ACL list_edit operation type for those fields
Harish
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2017 09:25 AM
I created the ACL for list_edit and related it to the whole table instead of just the field so it prevents anyone without itil access from using the List Editor as I don't see anyone inside our network making use of it without being in a support/fulfillment position.