Giving read/write access to Incident.comments_and_work_notes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-15-2017 11:32 AM
In an OOB instance, is there something preventing an individual with a custom role (not inherting other roles) from seeing and writing to the work notes field on the Incident record?
I created a read and a write role. It has my custom role requirement and no advanced script.
The work notes/comments field is added to the incident ESS view. However, my users with this custom role cannot see the field, much less write to it. Any idea what's blocking this access?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-15-2017 02:33 PM
Hi Eric,
Check if there are any ACLs on task.work_notes or incident.work_notes. Thats the only thing that controls write access on journal fields OOB.
I tested it in my OOB instance and can see user with custom role can see work_notes. The only change I did is add role to three acls on task.work_notes and user can see work_notes now:
If this doesnt work post your screesnhot
Shruti

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-15-2017 05:37 PM
Make sure your ACL is on the task level for [comments], and/or for [work_notes] fields if you want to give a user CRUD access to either of these.
This is different than the comments_and_work_notes field you added in your screenshot.