Action Permissions

All actions execute in the context of the ServicePlanner User. Grant the ServicePlanner User the permissions to access the functionality your actions rely on, such as Apex classes, flows, and prompt templates. Action permissions follow the guidelines in Common Access for Actions. Here are a few more details to keep in mind.

• Apex class access. Explicitly grant the ServicePlanner User access to each Apex class the action calls. Without it, the action fails with a generic error message.
• Apex sharing mode. Use actions that query customer data without sharing in the Apex class. If the class uses sharing, the query can return zero results with no error message.
• Object permissions. Grant Read access on any object the action queries. If the action also creates or updates records, add Create and Edit access.
• Field-level security. Object-level Read access isn't enough. Each field the action reads needs explicit Read access granted on the permission set. Without it, Salesforce returns blank values, which can look like a data problem but is a permissions issue.