- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2024 09:29 AM
I've created a report based off the sysevents table. However, non-admin users can't view the output of the report. I've created a new role, along with a new ACL (specifics below). However, when I add this role to a user, they are still unable to view the records. They see the message below.
ACL:
Type: Record
Operation: report_view
Protection Policy: None
Name: Event [sysevent]
Role added to ACL
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2024 09:52 AM
Hi @MStritt ,
-Check if the users have the access to view the table you are sharing
-Also ensure if the report are shared to the users having that role.
Refer this kb :https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0815218
Please mark this response as correct solution/ helpful if it helps you.Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2024 09:52 AM
Hi @MStritt ,
-Check if the users have the access to view the table you are sharing
-Also ensure if the report are shared to the users having that role.
Refer this kb :https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0815218
Please mark this response as correct solution/ helpful if it helps you.Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2024 10:32 AM
Hi Ramz,
-Check if the users have the access to view the table you are sharing
I thought giving the new role to this user and adding this new role to the new ACL mentioned above gave him the access to view the table? Or do I have to create a different ACL?
-Also ensure if the report are shared to the users having that role.
Yes, I've shared the report with the user.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2024 11:01 AM
I was able to resolve this.