Virtual Agent OOTB case conversation not working when user is not admin ie. create case
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
We have configured Virtual Agent for CSM and copied Out of the box conversations like create case and update case, however when we are testing it with non-admin user but has roles that can create cases the virtual agent is not processing the creation/update of cases.
Has anyone encountered similar scenario? What have you done to resolve it?
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago
Hello @ryev_a_ ,
Have you check which acl roles are applied on that table where you trying to create record via non-admin user ?
If this helps you then mark it as helpful and accept as solution.
Regards,
Aditya
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
36 seconds ago
hey @ryev_a_
This behavior is typically related to permissions and data access, especially when Virtual Agent topics are executed by non-admin users.
A few things you can check:
- ACLs on Case table
Even if the user has a role to create cases, Virtual Agent still enforces ACLs on the Case [sn_customerservice_case] table and its fields.
- Try impersonating the user and create a case manually.
- If it fails there, VA will also fail.
- Required roles / execution context
Virtual Agent runs in the context of the logged-in user (not admin).
- Ensure the user has appropriate CSM roles (e.g., customer/contact roles based on your setup).
- Mandatory fields / Data Policies
If you copied the OOTB topic, some required fields might not be handled.
- Check for Data Policies or mandatory fields that block insert/update.
- Reference data (Contact / Account)
Case creation often depends on valid Contact and Account.
- Verify the user has access to these records and they are being populated correctly.
- Debug logs
- Enable VA debug and review Conversation Logs (sys_cs_conversation_log) to see where it fails.
*************************************************************************************************************************************
If this response helps, please mark it as Accept as Solution and Helpful.
Doing so helps others in the community and encourages me to keep contributing.
Regards
Vaishali Singh
