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 check | Where in Setup (and supporting evidence) | What good looks like |
|---|---|---|---|
| 1 | Lead routing inputs, including Rating if used | Object Manager → Lead → Fields & Relationships; Lead report | Fields required by the intended routing rules are populated in the test cases. |
| 2 | Account classification, including Industry if used | Object Manager → Account → Fields & Relationships; Account report | Classification values match the rules the agent will use. |
| 3 | Opportunity next-step information | Object Manager → Opportunity → Fields & Relationships; open Opportunity report | The intended action has the information it needs, or an explicit missing-value path. |
| 4 | Contact email validity | Object Manager → Contact → Fields & Relationships; Contact report | Test recipients are valid and approved for the communication use case. |
| 5 | Required-field enforcement | Object Manager → affected object → Validation Rules | The relevant UI and API test cases enforce required business inputs. |
| 6 | Duplicate Contacts | Duplicate Rules and Matching Rules; duplicate report | Reviewed duplicate cases have a documented resolution or safe selection rule. |
| 7 | Duplicate Accounts | Duplicate Rules and Matching Rules; duplicate report | The action selects the intended account rather than an ambiguous match. |
| 8 | Custom fields used by the agent | Object Manager → affected object → Fields & Relationships | Every required field has an owner, meaning and usable test values. |
| 9 | Picklist consistency | Object Manager → affected object → Fields & Relationships | Active values and mappings agree with the agent's action rules. |
| 10 | Stale input records | Object Manager → affected object → Fields & Relationships; dated record report | The business owner has defined freshness rules and handling for stale records. |
| 11 | Grounding inputs, where configured | Agentforce Agents → selected agent; configured data source | A sandbox test returns the expected source-backed answer, including a missing-source case. |
| 12 | Required record relationships | Object Manager → affected object → Fields & Relationships; relationship report | Test records have required related records, or the action handles missing relationships. |
Process clarity: checks 13 to 22
| # | What to check | Where in Setup (and supporting evidence) | What good looks like |
|---|---|---|---|
| 13 | Opportunity stage entry criteria | Path Settings; Object Manager → Opportunity → Validation Rules | The process owner has documented when a record may enter each relevant stage. |
| 14 | Opportunity stage exit criteria | Path Settings; Object Manager → Opportunity → Validation Rules | Exit conditions are explicit and represented in acceptance tests. |
| 15 | Stage skipping | Object Manager → Opportunity → Fields & Relationships; stage history report | Allowed skips and forbidden transitions have separate test cases. |
| 16 | Rework and loop-back paths | Flows → relevant flow; record history | Repeated actions and reversals have a defined stopping or escalation path. |
| 17 | Flow ownership | Flows → relevant flow; owner register | A named person owns each flow invoked by an agent action. |
| 18 | Flow purpose | Flows → relevant flow → description | Inputs, outputs and business purpose are documented. |
| 19 | Lead qualification entry point | Flows; Object Manager → Lead → Validation Rules | The intended qualification path is documented and competing entry points are reviewed. |
| 20 | Renewal handoff | Flows → relevant renewal flow; handoff runbook | Trigger, receiving owner and exception handling are explicit. |
| 21 | Case escalation | Escalation Rules; Flows → relevant case flow | Escalation criteria and human handoff work in sandbox tests. |
| 22 | Process exceptions | Flows → relevant flow → decision elements | Exceptions have named owners and expected outcomes, not unwritten workarounds. |
Automation overlap: checks 23 to 36
| # | What to check | Where in Setup (and supporting evidence) | What good looks like |
|---|---|---|---|
| 23 | Active flows on agent-touched objects | Flows; Flow Trigger Explorer | Relevant active flows and their entry conditions are inventoried. |
| 24 | Workflow Rules overlapping flows | Workflow Rules; Flows | Still-running rules are accounted for and duplicate updates have a tested resolution. |
| 25 | Active Process Builder processes | Process Builder; Flows | Each active process has an owner and a tested migration or coexistence plan. |
| 26 | Apex and Flow updating the same field | Apex Triggers; Flows | Competing writers are identified and the final value is tested. |
| 27 | Multiple triggers on an object | Apex Triggers | Trigger interactions are reviewed rather than relying on an assumed execution sequence. |
| 28 | Validation and flow interactions | Object Manager → affected object → Validation Rules; Flows | Agent-triggered updates pass intended validations and fail safely otherwise. |
| 29 | Correct flow version activated | Flows → relevant flow → versions | The approved, tested version is active in the target environment. |
| 30 | Subflow dependencies | Flows → relevant flow → subflow elements | Referenced versions and failure paths are included in testing. |
| 31 | Flow failures | Paused and Failed Flow Interviews; flow error notifications | Relevant failures have owners and are resolved or explicitly block launch. |
| 32 | Bulk execution limits | Apex Test Execution; Debug Logs; sandbox bulk test | Representative volumes complete within limits without partial unintended work. |
| 33 | Hardcoded record IDs | Apex Classes; Flows → relevant flow | Environment-specific references are identified and tested in the target environment. |
| 34 | Queries inside loops | Apex Classes → referenced class | Code review covers query usage and a representative bulk test passes. |
| 35 | Record writes inside loops | Apex Classes; Flows → relevant flow | Code and flow review cover write volume and failure handling. |
| 36 | End-to-end action paths | Apex Test Execution; Flows → Debug; sandbox agent test | Success, 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 check | Where in Setup (and supporting evidence) | What good looks like |
|---|---|---|---|
| 37 | Identify the configured agent user | Agentforce Agents → selected agent; Users → Users → corresponding user | The worksheet names the configured user and the actions being tested. |
| 38 | Active user and appropriate license | Users → Users → agent user | The user is active and the assigned license supports the intended configuration. |
| 39 | Agent user role | Users → Users → agent user → Role; Roles | The role matches the intended record visibility. No higher role is granted just to hide an access failure. |
| 40 | Baseline profile access | Users → Users → agent user → Profile; Profiles → profile | Baseline grants are documented and broad administrative access is justified or removed through review. |
| 41 | Required object access | Permission Sets → assigned set → Object Settings; Profiles → profile → Object Settings | Required object operations are granted, and operations outside the use case are not added as a shortcut. |
| 42 | Required field access | Object Manager → affected object → Fields & Relationships → field → Set Field-Level Security; Permission Sets → Object Settings | Needed fields are visible or editable as required. Sensitive fields outside the use case remain restricted. |
| 43 | Record-level access | Sharing Settings; Roles; the specific sandbox record | The execution user can reach intended records and is denied access to out-of-scope test records. |
| 44 | Flow and Apex action access and context | Flows → referenced flow; Apex Classes; Permission Sets → Apex Class Access | Invoked actions have the required access. Their execution context is reviewed and tested for unintended privilege expansion. |
| 45 | Permission set group membership | Users → Users → agent user → Permission Set Group Assignments; Permission Set Groups | Group contents, muting and assignment status match the approved access design. |
| 46 | Allowed and denied action tests | Agentforce Agents → selected agent; sandbox tests using the configured execution identity | Required actions succeed and forbidden reads or writes fail. Record the user, action, expected result and actual result. |
| 47 | Check agent user access across all permission sets | Users → Users → agent user → Permission Set Assignments and Permission Set Group Assignments; Permission Sets → each assigned set | Review 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.