#Trailhead Challenges1,761 discussing

Hey Pavan, 

This is a standard Salesforce error tied to the user record specified (005dM00000h4XUT), meaning that user's email address hasn't been verified in the org. It's typically triggered when an action requires sending email (like Approval routing, Case assignment notifications, or an Agent action calling Send Email) and the target/owner user's email isn't verified. 

Fix: 

1. Setup > Users > find the user matching that Id (005dM00000h4XUT) 

2. Check the Email field, click Verify next to it 

3. Check that email's inbox, click the verification link 

4. Retry the action/challenge 

If this is your own Trailhead Playground user and you don't control that email inbox (common with auto-generated Playground emails), update the user's email to one you actually have access to first, then verify it. 

Reference:

@Omer Sela

Have you signed up the 

Developer Edition org with Agentforce for employees access

? 

Enable Agentforce Agents

Before you start creating agents, you first need to enable the building of agents and all of the required org features.

1. Click the Gear Icon and click Setup. The Setup page opens in a new tab.
2. In the Setup Quick Find box, search for and select Salesforce Go.
3. In the Search features box, search for and select Agentforce Studio.
4. Click Get Started and then click Turn On. This enables Einstein Setup and Agentforce Agents.
5. A popup box appears. Click Confirm.
6. Ensure the Turn on Agentforce Studio toggle is set to On.
7. Refresh your browser to reload Setup.

Initial Agent Setup

1. Click to open App Launcher, then search for and select Agentforce Studio.
2. From the Build menu, click Agents.
3. Click New Agent.
4. From the Or, start with a template section, find Agentforce Employee Agent and click Details. This shows you what comes with the template, including description, the Subagents, and Variables. This provides a good starting point.
5. Click Select Template.
6. For the Agent Name, add General Agent.
7. For Developer Name, General_Agent autopopulates.
8. Click Let’s Go.

Add Subagent to the Agent

For this Agent, you’re adding one additional Subagent from the asset library.

1. To the right of the Search box at the top, click the + icon, and select Add from Asset Library.
2. Find General CRM, click Select, and click Add to Agent. You now see General CRM in the Subagents list.
3. Click the right-facing arrow to the left of the General CRM subagent. This expands to show the actions associated with the subagent.
4. Hover over General CRM, click the + symbol, and select Add from Asset Library.
5. Find Summarize Record and click Select.
6. Click Add to Agent. You now see Summarize Record added to the list of actions under General CRM.

Remove a Subagent

Before you can test your agent, you need to remove the General FAQ subagent. This is because it uses Data 360, which in this environment is not enabled.

1. Hover over the General FAQ subagent, click the three dots, and select Delete.
2. In the popup window, click Yes, Delete. When you do this, the General FAQ subagent is now crossed out and red, providing you the ability to undo the deletion if needed. Leave this alone for now—when you save later on, this is removed.
3. Click Save.

Preview and Activate

Before activating the agent, it’s important to try it out and ensure it is working as intended.

1. From the middle section of the builder, click Preview.
2. Click the down arrow next to Live Test Mode. Just note that you have two options for testing your agent where you can either Simulate using mock data or run a Live Test using your live data. In this case click Live Test.
3. In the Let’s chat! box, enter "Provide me an overview of Edge Communications".
4. Read the information provided about Edge Communications. It might ask if you would like additional insights and you can continue answering or asking it questions if you’d like, but for this example you are not required to.
5. Click Save.
6. Click Commit Version and in the popup box click Commit Version.
7. Click Activate and in the popup box click Activate.

Grant Access to the Agent

With Agentforce for employees, you have control over who can access which agents. You can do this either by creating one or more permission sets, or by setting access within profiles. If you don’t grant access, even as the system administrator, you’re not able to use the agents you create. Your company wants you to create a permission set.

1. Click the Setup icon , then select Setup.
2. In the Setup Quick Find, search for and select Permission Sets.
3. Click New.
4. For the label enter "Grant Agent Access" and the associated API Name appears as "Grant_Agent_Access".
5. For the description enter "This grants access to the active Agentforce for employee agents".
6. Click Save.
7. Within the Apps section, scroll down and click Agent Access.
8. Click Edit.
9. You see a list of all active Agentforce for employee agents. Select General Agent and click Add, right arrow, to add it to the Enabled Agents section.
10. Once the General Agent is in the Enabled Agents section, click Save.
11. Click Manage Assignments then click Add Assignment.
12. Check the box next to your name, click Next, click Assign, and click Done.

Now you can see the agent icon on app. 

Thank you for the explanation.

The domain I'm using is my college's official domain (kristujayanti.com), and my email address was provided by my college. I don't own or manage the domain, so I don't have access to its DNS settings and can't add the TXT record required for domain verification. Since this is the college's domain, I also don't have the authority to request DNS changes, and even if I contact the IT department, it's unlikely they'll make such a change just for a Trailhead exercise.

Is there any alternative way to complete this module without verifying the domain? For example, can I temporarily change my email address to a personal email or another domain that I control and still complete the challenge?

If I do change the email address associated with my Playground or user account, will my progress in the module or Trailhead Playground be affected in any way, or is it safe to do so?

I'd appreciate any guidance. Thank you!

For your requirement, you can configure it through Organization-Wide Defaults (OWD) like this:

• Account & Contract: Set OWD to Public Read Only → this allows all users to view records but not edit them. 
• Opportunity: Set OWD to Private → only record owners and users higher in the role hierarchy will have access. 

Also, make sure your role hierarchy is properly configured, as it controls visibility for Opportunities in this case.

Let me know if you’re also using sharing rules or profiles, as they can override these settings.

@Parthsinh Rajavat  Permission Sets with Agent Access

is the right place to grant CRUD access to the required salesforce object. 

BUT for agent to do such work.. we need actions to be defined for the agent .. within Agentbuilder.. like query record actions or so.. 

below link is an example 

@Kiran Kharade - Vashi Integrated Solution Ltd depends on what you mean by "view CPQ report data."

If the users need to open reports that are built directly on CPQ objects such as CPQ Quotes, Quote Lines, Subscriptions, Contracts, or other SBQQ__ package objects, then report folder access alone will not solve it. They still need the required object, field, record, and package/license access behind those reports. Salesforce’s CPQ permissions guidance states that CPQ access is controlled through CPQ licenses and package-specific permission sets (Get Started with Salesforce CPQ Permissions)

Recommended option is to give CPQ licenses only to users who need direct access to CPQ records, then create a restricted read-only permission model for them as much as CPQ allows.

For non-CPQ users, the safer approach is not to expose the CPQ objects directly. Create a separate reporting layer, such as a custom reporting object, summary object, scheduled snapshot, CRM Analytics dataset, or exported BI dataset, containing only the fields they are allowed to see. Then report on that object/dataset instead of the live CPQ package objects. That gives visibility without opening full CPQ record access.

A dashboard with a running user may work for high-level summary visibility, but it should not be treated as a clean replacement for proper CPQ licensing or record access, especially if users need to drill into report details. 

My recommendation is: direct CPQ report access usually requires CPQ access. For non-CPQ users, create a controlled summary/reporting layer and expose only the required CPQ data there.