- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-07-2016 05:41 PM
Hi All,
I have been trying to make the change calendar visible to all users via the Public role. I can get this to work by setting the Change Request [change_request] -- None -- as read only to the Public role and this I can see works as expected. But from my understanding this gives public users read access to all fields in the change_request table? I was trying to limit the rows that they can see, but when I do this they do not see the changes on the calendar. Instead they get an empty calendar with Number of rows removed by Security constraints: x
I tried setting the change number, short description and planned start to all be visible by the Public role but still no luck. Does anyone know what columns I need to make visible so it can be seen on the calendar?
Secondly, when the CR is visible on the calendar, is there a way to make it so that it is not a link? By default it is a link to take you to the details of the CR.
Regards
James
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-09-2016 03:57 AM
Do they have read access to the record (e.g. change_request.none)? You'll need that if you want to grant read access to individual fields as well. Your ACLs should look something like this
change_request.none - record level access, grant read access to everyone (role=public)
change_request.* - all fields, grant read access to only those whom you deem necessary (e.g. roled users or logged in users? your choice)
change_request.field_name - a specific field like number, short_description, grant access to everyone (role=public)
Using Access Control Rules - ServiceNow Wiki
Security Best Practices - ServiceNow Wiki
Contextual Security - ServiceNow Wiki
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-10-2016 03:45 AM
I do not see any property or setting to disable that.
I invite you to open an enhancement request! Our product managers DO listen.
Enhancement requests: Tell us how you would improve the ServiceNow product
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-10-2016 05:12 PM
Thanks Chuck for all your assistance.
Cheers
James
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-06-2018 09:30 PM
Hey Chuck
I tried this and found it works, though my question is around if 'Public' is technically considered a role by ServiceNow?
Thanks
Chris
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-07-2018 06:47 AM
It's a role, but not one you assign to people. It's used to assign to the things you want to grant access to.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-19-2020 12:53 PM
Hey Chuck,
Using
change_request.none - record level access, grant read access to everyone (role=public)
gets the job done, but it of course leaves your change calendar open for the public to see. You mention that you can also grant read access to only those you deem necessary (i.e. logged in users) Is that done via script? If I don't want role=public, but only authenticated users, how would I do that?
Donald
