#Salesforce Admin366 discussing

Hi , 

Ensure that you're working in the Lightning App Builder and editing the correct page layout for the Account object.

Upgrade to Dynamic Forms

When you click on the Record Detail component and select Upgrade Now, make sure the page is upgraded to use dynamic forms. Without this step, you won't see the option to customize field sections.

Add the Field Section

Drag the Field Section component from the palette to the desired spot in the Details tab. After adding it:

• Click on the new section.
• In the properties pane, type "Sales Region" in the Label field. You don’t need to "find" it in a list—it’s just a text input.

Save and Activate

After customizing, click Save, and if required, activate the page for the right app or profile.  

We have had luck in resolving this a few ways. 

• Selecting the 'Generate new password and notify user immediately' checkbox. 
• Generating a temporary verification code and sending to them. 

Otherwise you may need to reach out to Salesforce support to get help. There was a bug that says it has been fixed. Users are not able to change and verify their emails in all Orgs after Summer 26 release | Issue Details | Salesforce Help

Either way, it also explains other options that may help unstuck your non admins in a Sandbox. 

Hi @Naresh Kumar Ojha

, 

You can run the following in the anonymous window to see the see names of the classes that are invalid:  

List<ApexClass> invalidClasses = [ 

    SELECT Id, Name  

    FROM ApexClass  

    WHERE IsValid = false 

]; 

for (ApexClass cls : invalidClasses) { 

    System.debug('Invalid Class: ' + 

cls.Name

); 

}

Hi Cat,

This behavior happens because of how Salesforce handles rejections that route back to previous steps in multi-step approval processes. When Step 2 rejects and sends the record back to Step 1, Salesforce re-evaluates the step criteria and re-assigns the record to the Step 1 approver, which automatically triggers the main Approval Assignment Email Template defined at the process level, right alongside your custom rejection email.

Here is how you can clean up that duplicate notification behavior:

1.Review the Approval Assignment Template Setting:Process-Level Template. 

Check the top-level Approval Assignment Email Template configured on your Process Definition Detail page. This template fires every time a record is assigned or re-assigned to an approval step. You can verify success by noting whether changing or clearing this default template alters what emails are dispatched upon re-assignment.

2.Adjust Step-Level Rejection Actions:Step Reject Behavior. 

Instead of relying on standard step rollbacks that re-trigger assignment emails, consider configuring specific rejection actions (such as Field Updates or custom Email Alerts) to handle status changes explicitly, or route the rejection to a final rejection handler rather than looping back to Step 1. You can verify success when a rejected record updates the status without dispatching the initial request template a second time.