- We have limited Flex Credits and want to make them available for all users in our Salesforce org.
- We have created a Prompt Template and are invoking it from a Record-Triggered Flow.
- We want to execute the prompt under a specific user context instead of allowing every user to execute it independently.
- If we assign the Prompt Template User permission to a specific user and configure the flow to run in that user's context, will the prompt execute successfully?
- Will this approach help us control or reduce Flex Credit consumption when multiple users trigger the flow?
- Are there any licensing or permission requirements, such as the AI unmetered user license or Prompt Template User permission, that could prevent the prompt from executing?
- Is there a recommended Salesforce-supported approach to allow all users to benefit from the prompt while managing limited Flex Credits?
- Are there alternative solutions, such as a dedicated integration user, asynchronous Flow execution, or another automation design, to achieve this?
We would appreciate guidance on the recommended approach, including any limitations or best practices for managing Flex Credits when Prompt Templates are invoked through Record-Triggered Flows.
#Agentforce #Prompt Builder #Mvp-agentforce-prompt-builder-team
1 件の回答
Hi @Sourabh Dondekar Good question! Using a dedicated user for Prompt Template execution can help manage access, but it won't directly reduce Flex Credit consumption.
A few suggestions:
- Flex Credits: Usage depends on billable AI executions, not the number of users.
- Running User: Record-Triggered Flows don't allow you to directly select a specific running user.
- Permissions: Make sure the execution context has the required Prompt Template permissions and access.
- Flow Optimization: Trigger the prompt only when necessary, using entry conditions and field-change checks.
- Asynchronous Flow: Helps manage processing but doesn't reduce credit consumption by itself.
- Monitoring: Use Digital Wallet to monitor usage and identify unnecessary executions.
My suggestion: Focus on reducing unnecessary prompt calls rather than restricting users. You can also consider a centralized automation approach for better control.
Hope this helps!
