snc_read_only User being able to create Reports

[samuelbingham]

Hello all, I want a user with the snc_read_only role to be able to make reports. Is there any workaround for this? 

[Robbie]

Hi @samuelbingham,

(Updated)

As you've probably read from the SN Docs site, the read-only role (snc_read_only) restricts a user or a group of users to read-only access on the tables to which the user already has access.

Its purpose is to restrict actions like the insert, update, or delete operations on the tables accessible through their existing roles.

After you assign this role to a user, they can no longer create, update, or delete records on ANY tables.

As far as a workaorund, you would need to update the base ACL's appropriately, however this would not be best practice and could be and most likely in violation of the role.

Whilst I understand the ask, the read only role is seen as an auditor type role and only permits read only access.

@samuelbingham- Updated - If for example you wish to grant read access to Incident records (and related tables), you could grant the user the following roles:

- sn_incident_read

- report_user (or report_admin depending on report access required)

To help others (and for me to gain recognition for my efforts), please mark this response correct by clicking on Accept as Solution and/or Kudos.



Thanks, Robbie

https://www.servicenow.com/docs/bundle/yokohama-platform-administration/page/administer/user-adminis...

[Viraj Hudlikar]

Hello @samuelbingham 

See main purpose of this role is grant read-only access across instance, now if you allowing to create report then what's use of this ootb role. If you really need this badly then you will need to create acl on report which will allow to create reports but again this snc_read_only will override and will block your purpose. Better to halt and remove this role and grant normal role which allows to create report in instance.

If my response has helped you hit helpful button and if your concern is solved do mark my response as correct.

Thanks & Regards

Viraj Hudlikar.