Restrict fields through ACL
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi @Devansh00
You can achieve this by creating a field-level Read ACL on incident.short_description.
A field specific ACL takes precedence over the generic incident.* ACL, so only the Short Description field will be hidden while users can still access the rest of the Incident record.
I tested this in my PDI, and it worked as expected. I've attached screenshots for reference.
If this helps solve your requirement, please mark the response as Helpful and Accept it as the solution.
Regards,
Dimple Shaik
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hello @Devansh00 , Create a field-level Read ACL for incident.<field_name>. Add required roles other than itil, ensuring ITIL users do not possess those roles.
Prerequisite: Confirm no conflicting field-level ACLs currently exist on incident.<field_name>.
Regards,
Nishant
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
To hide the field from ITIL users, create a field-level Read/Write ACL explicitly targeting incident.short_description that denies access to the itil role, or use a UI Policy / Client Script with g_form.setDisplay('short_description', false) to remove it from the form layout.
This helps other users find accurate and useful information more easily