How to add Edit(bulk ) button for legal requests in legal workspace list view Issue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The intent is to select multiple records and apply bulk update, including Assigned to / Assignment group fields, in one action by enabling Edit multiple action in the legal counsel workspace. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } N/A Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } OOB Edit declarative action is not showing up on the list is due to the "Requires write access" field that is set to true on the declarative action. https://instance>.service-now.com/now/nav/ui/classic/params/target/sys_declarative_action_assignment.do%3Fsys_id%3D4a9232b273131010a0a79329faf6a732%26sysparm_view%3Dadvanced For the legal requests table (sn_lg_ops_request), there are ACLs in place that determine a user's write access on a per-record basis. This can be seen by running a background script with the following content: try { session.onlineImpersonate("sys_id"); // sysId of legal counsel role users var gr = new GlideRecord("sn_lg_ops_request"); gs.info('User has table-level write access: ' + gr.canWrite()); } finally { session.onlineUnimpersonate(); } The call to gr.canWrite() will return false, which explains why the Edit button is not showing up. This OOB ACL (https://<instance>.service-now.com/nav_to.do?uri=sys_security_acl.do?sys_id=c8a79c80b7453010d7f1ee58de11a99e) is the most permissive. However, it requires that active is set to true on the record. Because this is not true for the whole table, the condition is not met. There may be records that show in the list that the user does not have permission to edit, and it won't necessarily be clear as when selecting multiple records to edit which ones are read-only or editable. Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } one possible solution to this is to duplicate the Edit declarative action and create a version specifically for the legal requests table, which has "Requires edit access" set to false but has 'required roles' set to what would be most fitting for a user likely to bulk edit records (as an example, sn_lg_ops.request_fulfiller and sn_lg_ops.request_manager). If the user selects a record they do not have edit access for while selecting multiple requests, then they will see that all fields in the multi-edit form show as read-only, but for cases where they have selected records they have permission to edit, the form will display correctly