I'm trying to utilise the pre-built ServiceNow actions in CoPilot Studio.
I have setup a connection in Power Platform that uses basic authentication which uses the System Admin account credentials of my DEV SN instance.
I want to be able to use the Users context though and only surface records that the logged in user has access too.
Using copilot author auth in the CoPilot action works fine but will surface all records based on the fact it users the Power Platform connection which is the system admin account.
Using user auth in the CoPilot action fails. How can i get this to work to use the users context does the power platform connection need to be something other than basic?
This was my concern also. I was hoping to avoid having to filter but looks like I will have to do it this way for now. I even used the oauth2 authentication type and it still just uses the account that you initially setup the connection with. Doesn't prompt the user to authenticate.
I see that for ServiceNow connector, there's no option to define User or Copilot author context, thus it means that if you define a connection, then it's being used by everyone. Overall in that case I'd suggest you to use a service account with full set of privileges and filter the tickets based on the user information. Bot should have the access to Entra ID user information - it can use it to filter out the tickets. I don't see any other option for this for now.
In case of any other questions, let me know. If the answer helped you, mark it, so that others can benefit from it.
Best regards,
Artur Stepniak
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
2
Share
Report
All responses (
Answers (
