---
schema_version: "1"
id: 9d277411c75ba3f7806ed26928ae053219642605a40bddaa63dd809c036e43c2
title: Action Permissions
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/sp_actions_permissions.md
canonical_url: https://help.salesforce.com/s/articleView?id=service.sp_actions_permissions.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 190c33ab8aee0c68f201395e2c4b118652f3a6aa7fd38b71544ed33501cbd26a
description: Actions run under the ServicePlanner User's permissions. Grant the access that your actions require so that they can run.
release: "264"
---
# Action Permissions

Actions run under the ServicePlanner User's permissions. Grant the access that your actions require so that they can run.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;"><a href="https://help.salesforce.com/s/articleView?id=service.einstein_service_intro.htm&amp;language=en_US" target="_blank">View supported editions</a>.</td></tr></tbody></table>

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](https://help.salesforce.com/s/articleView?id=ai.agent_actions_common_perms.htm&type=5&language=en_US). 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.