There is a client requirement which requires Read-only access to entire ServiceNow Environment

[Rajendra Korada]

There is a client requirement which requires Read-only access to entire ServiceNow Environment.

Client requires an appropriate role which allows Read/View only level access to the ServiceNow environment. (Same as admin who can access to all CRUD operations in instance) but with Read only.

Is it best practice to use snc_read_only role? Any roadblocks or precautions or alternatives to proceed with snc_read_only role?

Please suggest.

[Mark Roethof · Accepted solution]

Hi there,

snc_read_only sounds to be your goto. It has some small downsides though, for example even creating a favorite won't be possible anymore, since the user has read only 😂

[Rajendra Korada]

Hi There,

A small doubt: Can the snc_read_only role be given to a user who doesn't have any role previously.

As such my understanding is that the snc_read_only role is to restrict the access to the user who already has access.

In Servicenow doc: 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.

Please clarify

[Mark Roethof]

snc_read_only would be in combination with an other role, for example the admin role. So you have a read-only admin.

Do be aware, it does cost licensing, even through its just read-only admin for example, or read-only itil.