Skip to main content
All checklists

Salesforce Checklist · AI Readiness

Agentforce Readiness 47-Point Checklist (2026)

The 47-point check before you launch Agentforce, now with agent user access: role, object and field access, and permission sets the agent needs.

Clientell AI team·May 20, 2026·06 sections
What's inside

Score

0/100
47
87
Agent
65
Record
78

Checklist·Read

Agentforce Readiness 47-Point Checklist (2026)

Written for Salesforce admins and teams

LytxTalkspaceNuloPixisAppsmithCoreViewConstella IntelligenceGoviniSunbelt SolomonSafety VisionCurrier PlasticsIESVEGlobusGushworkIrys AIProdigyPAM HotelsPalletized TruckingDallas HabitatRIM AllianceStonewood PartnersEncore FocusCreatiquetechSkyaLynx9DeploidDGAOppcoLytxTalkspaceNuloPixisAppsmithCoreViewConstella IntelligenceGoviniSunbelt SolomonSafety VisionCurrier PlasticsIESVEGlobusGushworkIrys AIProdigyPAM HotelsPalletized TruckingDallas HabitatRIM AllianceStonewood PartnersEncore FocusCreatiquetechSkyaLynx9DeploidDGAOppco

Before launching Agentforce, check the data, process, automation and permissions behind each intended action. This worksheet keeps the existing 47-point format and adds an agent user access review. It is a manual review aid, not a Salesforce certification or a guarantee of launch readiness.

Salesforce Help lists “Agent can't access data” alongside “Agent user role & object access” in its Agentforce readiness guidance, article 005317651. The worksheet below turns that troubleshooting prompt into checks you can record and repeat. The specific acceptance criteria are our suggested review steps, not requirements quoted from Salesforce.

How to use this worksheet

For each numbered item, record Pass / Fail / Not applicable, evidence, owner and retest date. Explain every not-applicable decision. Setup labels can vary by edition and enabled features. Where a check needs record evidence, use Reports or a sandbox test alongside Setup.

Copy this evidence line for each item: Item: ___ | Status: ___ | Evidence: ___ | Owner: ___ | Retest date: ___. Do not put customer record data or credentials in a shared worksheet.

Data quality: checks 1 to 12

#What to checkWhere in Setup (and supporting evidence)What good looks like
1Lead routing inputs, including Rating if usedObject Manager → Lead → Fields & Relationships; Lead reportFields required by the intended routing rules are populated in the test cases.
2Account classification, including Industry if usedObject Manager → Account → Fields & Relationships; Account reportClassification values match the rules the agent will use.
3Opportunity next-step informationObject Manager → Opportunity → Fields & Relationships; open Opportunity reportThe intended action has the information it needs, or an explicit missing-value path.
4Contact email validityObject Manager → Contact → Fields & Relationships; Contact reportTest recipients are valid and approved for the communication use case.
5Required-field enforcementObject Manager → affected object → Validation RulesThe relevant UI and API test cases enforce required business inputs.
6Duplicate ContactsDuplicate Rules and Matching Rules; duplicate reportReviewed duplicate cases have a documented resolution or safe selection rule.
7Duplicate AccountsDuplicate Rules and Matching Rules; duplicate reportThe action selects the intended account rather than an ambiguous match.
8Custom fields used by the agentObject Manager → affected object → Fields & RelationshipsEvery required field has an owner, meaning and usable test values.
9Picklist consistencyObject Manager → affected object → Fields & RelationshipsActive values and mappings agree with the agent's action rules.
10Stale input recordsObject Manager → affected object → Fields & Relationships; dated record reportThe business owner has defined freshness rules and handling for stale records.
11Grounding inputs, where configuredAgentforce Agents → selected agent; configured data sourceA sandbox test returns the expected source-backed answer, including a missing-source case.
12Required record relationshipsObject Manager → affected object → Fields & Relationships; relationship reportTest records have required related records, or the action handles missing relationships.

Process clarity: checks 13 to 22

#What to checkWhere in Setup (and supporting evidence)What good looks like
13Opportunity stage entry criteriaPath Settings; Object Manager → Opportunity → Validation RulesThe process owner has documented when a record may enter each relevant stage.
14Opportunity stage exit criteriaPath Settings; Object Manager → Opportunity → Validation RulesExit conditions are explicit and represented in acceptance tests.
15Stage skippingObject Manager → Opportunity → Fields & Relationships; stage history reportAllowed skips and forbidden transitions have separate test cases.
16Rework and loop-back pathsFlows → relevant flow; record historyRepeated actions and reversals have a defined stopping or escalation path.
17Flow ownershipFlows → relevant flow; owner registerA named person owns each flow invoked by an agent action.
18Flow purposeFlows → relevant flow → descriptionInputs, outputs and business purpose are documented.
19Lead qualification entry pointFlows; Object Manager → Lead → Validation RulesThe intended qualification path is documented and competing entry points are reviewed.
20Renewal handoffFlows → relevant renewal flow; handoff runbookTrigger, receiving owner and exception handling are explicit.
21Case escalationEscalation Rules; Flows → relevant case flowEscalation criteria and human handoff work in sandbox tests.
22Process exceptionsFlows → relevant flow → decision elementsExceptions have named owners and expected outcomes, not unwritten workarounds.

Automation overlap: checks 23 to 36

#What to checkWhere in Setup (and supporting evidence)What good looks like
23Active flows on agent-touched objectsFlows; Flow Trigger ExplorerRelevant active flows and their entry conditions are inventoried.
24Workflow Rules overlapping flowsWorkflow Rules; FlowsStill-running rules are accounted for and duplicate updates have a tested resolution.
25Active Process Builder processesProcess Builder; FlowsEach active process has an owner and a tested migration or coexistence plan.
26Apex and Flow updating the same fieldApex Triggers; FlowsCompeting writers are identified and the final value is tested.
27Multiple triggers on an objectApex TriggersTrigger interactions are reviewed rather than relying on an assumed execution sequence.
28Validation and flow interactionsObject Manager → affected object → Validation Rules; FlowsAgent-triggered updates pass intended validations and fail safely otherwise.
29Correct flow version activatedFlows → relevant flow → versionsThe approved, tested version is active in the target environment.
30Subflow dependenciesFlows → relevant flow → subflow elementsReferenced versions and failure paths are included in testing.
31Flow failuresPaused and Failed Flow Interviews; flow error notificationsRelevant failures have owners and are resolved or explicitly block launch.
32Bulk execution limitsApex Test Execution; Debug Logs; sandbox bulk testRepresentative volumes complete within limits without partial unintended work.
33Hardcoded record IDsApex Classes; Flows → relevant flowEnvironment-specific references are identified and tested in the target environment.
34Queries inside loopsApex Classes → referenced classCode review covers query usage and a representative bulk test passes.
35Record writes inside loopsApex Classes; Flows → relevant flowCode and flow review cover write volume and failure handling.
36End-to-end action pathsApex Test Execution; Flows → Debug; sandbox agent testSuccess, denied access, missing input and error paths have recorded results.

Agent user access: checks 37 to 47

Start with the actual execution identity for each action. Do not assume that a successful administrator preview proves the agent user can access the same records. Review action execution context separately, especially for Flow and Apex.

Service agents run as the agent user set on the agent. Employee agents run as the person using them, so run checks 38 to 47 against a representative user for each profile that will use the agent.

#What to checkWhere in Setup (and supporting evidence)What good looks like
37Identify the configured agent userAgentforce Agents → selected agent; Users → Users → corresponding userThe worksheet names the configured user and the actions being tested.
38Active user and appropriate licenseUsers → Users → agent userThe user is active and the assigned license supports the intended configuration.
39Agent user roleUsers → Users → agent user → Role; RolesThe role matches the intended record visibility. No higher role is granted just to hide an access failure.
40Baseline profile accessUsers → Users → agent user → Profile; Profiles → profileBaseline grants are documented and broad administrative access is justified or removed through review.
41Required object accessPermission Sets → assigned set → Object Settings; Profiles → profile → Object SettingsRequired object operations are granted, and operations outside the use case are not added as a shortcut.
42Required field accessObject Manager → affected object → Fields & Relationships → field → Set Field-Level Security; Permission Sets → Object SettingsNeeded fields are visible or editable as required. Sensitive fields outside the use case remain restricted.
43Record-level accessSharing Settings; Roles; the specific sandbox recordThe execution user can reach intended records and is denied access to out-of-scope test records.
44Flow and Apex action access and contextFlows → referenced flow; Apex Classes; Permission Sets → Apex Class AccessInvoked actions have the required access. Their execution context is reviewed and tested for unintended privilege expansion.
45Permission set group membershipUsers → Users → agent user → Permission Set Group Assignments; Permission Set GroupsGroup contents, muting and assignment status match the approved access design.
46Allowed and denied action testsAgentforce Agents → selected agent; sandbox tests using the configured execution identityRequired actions succeed and forbidden reads or writes fail. Record the user, action, expected result and actual result.
47Check agent user access across all permission setsUsers → Users → agent user → Permission Set Assignments and Permission Set Group Assignments; Permission Sets → each assigned setReview every direct assignment and every set in assigned groups alongside the profile. Record which source grants each sensitive object, field and system permission. Removing one grant is not treated as proof that access is gone elsewhere. Retest both allowed and denied actions.

Make the launch decision from evidence

Do not turn a count of passed checks into a promised success rate. An unresolved permission failure can block an action even when every data-quality check passes. Give each failure an owner, agree which failures block launch, and repeat the affected tests after changes.

For a broader permissions review, see the Salesforce permissions audit. To inspect the surrounding org, see the Agentforce readiness audit.

Start the 14-day Platform trial, no card. Run an access review of your production org yourself. Nothing changes without your approval.

Stop reading. Start shipping.

Put this resource to work with a Platform trial.

Use this resource to guide your own Salesforce work. Try Clientell AI Platform free for 14 days, starting at your first org connection. No credit card required. Nothing changes without your approval.

How to use this resource

  • Review the guidance against your org's needs.
  • Confirm requirements with the people responsible.
  • Test proposed changes before approving them.
  • Document decisions and follow-up work.

Topics covered

From this checklist

AI ReadinessAdminsArchitectsRevopsLeadersAgentforceAI AgentsFlow BuilderApexData CloudPermissionsBest Practices

Section index

Jump to any section.

Deep-link to a specific part of this checklist, or copy the URL to send the whole thing to a teammate.

Sections

06

in this checklist

  1. /01

    How to use this worksheet

  2. /02

    Data quality: checks 1 to 12

  3. /03

    Process clarity: checks 13 to 22

  4. /04

    Automation overlap: checks 23 to 36

  5. /05

    Agent user access: checks 37 to 47

  6. /06

    Make the launch decision from evidence

Share this checklist

Send the URL to your team. Anchors preserved.

Getting Started

Ready to transform your Salesforce?

Clientell AI is the AI agent for Salesforce admins and teams. It asks before it changes anything in production. Start a 14-day free trial, no credit card.

14-day free trial  ·  No credit card required

SOC 2
HIPAA
ISO 27001
Salesforce Partner