How can snc_internal users view their submitted cases on the portal.

Anup Desai1
Mega Sage

Hi all,

We’ve created a record producer that creates a case in the sn_customerservice_casetable.

Our requirement is for users with the snc_internal role to be able to view the cases they have submitted via the esc portal. However, with only the snc_internal role, they are unable to see any of their cases.

We do not want to assign them business_stakeholder roles due to licensing concerns. Is there another CSM-specific role or configuration we can use to allow snc_internal users to view only the cases they have submitted?

Any suggestions or best practices would be appreciated.

Thanks in advance!

1 ACCEPTED SOLUTION

Anup Desai1
Mega Sage

Hello all,

We have assigned sn_customerservice.self_contributor.
It enables users with the snc_internal role to create cases for themselves.
Capabilities of self_contributor:
The capabilities granted by the sn_customerservice.self_contributor role primarily focus on the user's ability to manage their own requests.
◦ Create cases on their own behalf, including cases for catalog items.
◦ Create cases from various communication channels (phone, web, chat, Virtual Agent,
messaging).
◦ View and follow up on cases they have created for themselves.
◦ Add additional comments and attachments.
◦ Accept or reject a solution.
◦ Close a case.
◦ Receive notifications of case updates.
◦ Read work notes.


In the Application Navigator, enter license_role.list to open the Subscription
Roles table.
1. Click the Personalize List (gear icon) to customize visible fields.
2. Select Name, Application, and Role Type to view each role, the application it's tied to,
and its classification.
Role Types & Licensing:
● Fulfiller (FF) Role: Grants full access to view and update all cases. Users assigned this
role will consume a Fulfiller license.
● Business Stakeholder (BSH) Role: Allows users to view all cases but not update them.
Users consume a BSH license if this is their highest assigned role.
● Requester Role: Users can only view and update their own cases. This role does not
consume a license on most role-based products like CSM (however, there’re a few
products that include Requesters)

View solution in original post

6 REPLIES 6

Maik Skoddow
Tera Patron
Tera Patron

Hi @Anup Desai1 

 

Assign the sn_customerservice.case_viewer Role to snc_internal Users. This role is designed for internal users who need readonly access to cases. It allows users to view cases without editing rights, similar to the business_stakeholder role but intended for internal users. You may need to adjust Query Rules and ACLs to ensure that users with this role can only see cases they have submitted (i.e., where the user is the requester or contact)

 

Maik

Thank you, this allows us to see the cases, but in addition we need for them to edit: Chat with Agent (Add comments ), Attach Documents, etc. We want to mirror the behavior as Requestor for Incidents and Requests. These do not require a paid license.

TedN
Tera Contributor

Have you looked at using sn_customerservice.requester role?

It is mentioned in parallel with Unified Consumer in the documentation.

It's seems to be one of few roles (in CSM) that can be combined with snc_internal.

I haven't tested it properly yet but it's on the 'to-do-list'.

 

https://www.servicenow.com/docs/bundle/zurich-customer-service-management/page/product/customer-serv...

 

Docs mentions the combo snc_internal and different roles and features but not much is written about sn_customerservice.requester in combination with snc_internal. 

 

can you confirm the source for this recommendation? license_role table defines sn_customerservice.case_viewer role as falling under Business Stakeholder, which is chargeable.

case_viewer.png

I separately looked into sn_customerservice_team_member table which allows correlation between any Account and User (not just Contact), however I'm surprised OOTB there are no ACLs & Before Query Business Rule that would be reading from these table to allow visibility. which points me towards being unsure how this is addressed on licensing level.