Assignment Group

Ralton Stewart · ‎11-13-2023

Hello Community we created a new Assignment group Developers, the purpose of this group was to allow Developers to view tickets in read only, I added the the snc_read_only role and it appears to work as expected.

Today I was contacted by 3 members of that group it appears that the snc_read_only is appearing in their profile and they are unable to submit tickets from the portal page. I did not expect this how can I get round it?

with the read-only role

read only removed

Sandeep Rajput · ‎11-13-2023

@Ralton Stewart snc_read_only role allows users to read the ticket details, as this is a read only role, users will not be able to create incidents neither on backend nor on the portal.

Here is the excerpt from the now support article

Adding this role to a user or group on the instance will cause all users with this role to immediately have read-only access to any tables they could previously modify or otherwise manipulate.

The snc_read_only role provides no additional permissions to the individual or group to whom it is assigned (read or otherwise). This role is normally used together with one or more other roles. This role will simply prevent the user from inserting, modifying, or deleting records in tables that the user currently has access to by virtue of other roles or permissions on the instance.

Source: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0748343

View solution in original post

jonsan09 · ‎11-13-2023

According to the ServiceNow support site it appears to be the intended functionality of the 'snc_read_only' role. It will not grant any additional access but instead restrict existing access to read only:

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0748343 .

For providing read only access you may want to look into using the ITSM roles plugin (there might be licensing implications with this option, check with your reps)

https://docs.servicenow.com/bundle/vancouver-it-service-management/page/product/incident-management/...

Or the other option would be to create some ACLs on the tables you want those developers to have read only access to.

Sandeep Rajput · ‎11-13-2023

@Ralton Stewart snc_read_only role allows users to read the ticket details, as this is a read only role, users will not be able to create incidents neither on backend nor on the portal.

Here is the excerpt from the now support article

Adding this role to a user or group on the instance will cause all users with this role to immediately have read-only access to any tables they could previously modify or otherwise manipulate.

The snc_read_only role provides no additional permissions to the individual or group to whom it is assigned (read or otherwise). This role is normally used together with one or more other roles. This role will simply prevent the user from inserting, modifying, or deleting records in tables that the user currently has access to by virtue of other roles or permissions on the instance.

Source: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0748343