When considering the myriad of options within a Salesforce org’s Setup, one may easily become overwhelmed by the sheer possibilities of what to explore next. While most admins are extremely familiar with the functionalities they use day in and day out (such as report types), Setup may not be the first place that comes to mind when checking out what’s new or what else can make their lives easier.
In this article, we’ll explore a few Setup pages alongside newer and older functionalities that are worth knowing about and leveraging within your organization.
Optional Salesforce Functionality
Salesforce came up with many notable enhancements and additional products in the last few years for Salesforce professionals to use in order to build scalable processes and user-friendly experiences. This, however, doesn’t mean that everything has to be used for every project or scenario. There might be situations when you didn’t know a functionality existed until you needed it – and as always, less can be more.
Additionally, new Setup pages will become available based on the Salesforce products you purchased or that are included in your edition, and that you chose to turn on.
Let’s deep dive into five Setup pages that are sure to come in handy!
1. Process Automation Settings
While you may be familiar with process automation settings, there is one setting that may often be overlooked as it is not available in the production environment.
As a best practice, however, even if you are just getting started with Salesforce Flow or are already an expert at leveraging Flow Builder for complex processes, the development and testing of any Flow should happen in sandboxes prior to being ready to move it into production.
The ability to Run Flow as Another User (assuming the Flow is not running in system context) will ensure that everything works as intended and the user’s profile or permission sets grant them the right access to leverage the new process.

Once the setting is enabled, it’s as simple as you would think to make use of it. You only have to debug the Flow you would like to test, select the user and the triggering record.
Then hit “Run”.

2. User Management Settings
User is one of the core Salesforce objects that all admins are bound to work with from early on. Making sure that your users are properly set up with the right object and field permission should always be strongly considered. This is why this new User Settings option is bound to become your ultimate time saver when creating new fields or editing access for existing ones.
Field-Level Security for Permission Sets During Field Creation is that one functionality you have been waiting for since permission sets and permission set groups became the preferred go-to due to their flexible nature. This can be switched on within the User Management Settings page – you will potentially save dozens of clicks with just a flick of a switch!

According to the functionality description, this feature is available when creating and editing custom fields. However, you can still view the permission set access for standard fields and even edit the access to some of them. For example, you can only view the permissions for Lead Status, but you can both view and edit the permissions for Account Site.


To explore a few more functionalities related to user management, make sure to take a look at the post linked below!
3. Deployment Status
Within the Salesforce Setup, the Deployment Status page is the clear go-to for monitoring your deployment progress. From change sets or Metadata API deployments, they will all be captured on this page, with the possibility of following them in real time.
Visual representation will be available when deployments are in progress to denote the total number of components, how many were processed out of the total, and if there were failures.
A similar chart will also be displayed for Apex tests that are supposed to run. These charts will remain available even after the deployment is completed.

Additionally, you are able to dive into successes but, more importantly, into the failed deployments’ errors to find out what went wrong and adjust the components accordingly before retrying the deployment. On this same page, if you opt to validate your components first and deploy them at a later time, Quick Deploy will become an option as long as the validation is successful.
Find out everything about the Deployment Status page here.

4. Email Deliverability
Sending emails from Salesforce is something that most likely all Salesforce customers use for various purposes, be it external emails or internal notifications.
While it is highly unlikely you will need to change this setting in production, you should be aware of it while developing and testing in sandboxes.
The Access to Send Email is set to “All email” by default in all non-sandbox orgs, and to “System email only” for new and refreshed sandboxes. Here’s what these mean:
- No access: Prevents all outbound emails to and from users, with the exception of password reset emails.
- System email only: Allows only automatically generated emails, such as new user emails.
- All email: Allows all outbound emails.

“System email only” is used for sandboxes to prevent any rogue emails from being sent out by mistake while testing, especially in a Partial or Full Copy sandbox that might have real data that wasn’t anonymized or had the email addresses invalidated.
At the same time, if you would like to test a functionality that implies emails having to be delivered, don’t forget to take a look at this setting first!
5. Organization-Wide Email Addresses
As a Salesforce Admin, chances are that this is a requirement you have already encountered. If not, you likely will – especially in an organization that does have to keep in direct contact with customers or prospects outside of the sales team.
The need for a shared email address to be used by multiple people when sending out emails is a well-known scenario for support teams, especially when 24/7 coverage is needed on an issue.
The Organization-Wide Email Addresses page in Setup is where you can navigate to define such email addresses, which can be easily selected by users who are assigned a certain profile or permission set.
On top of the optional feature above, as of Summer ’23, Salesforce enforced the need to have a “Default No-Reply Address” set in your org for case-related notifications.

Make sure to review the considerations of using this functionality in order to make the most out of it.
Summary
All in all, these have been only a few of the Setup pages that can help you, as a Salesforce Admin, optimize your work, save time, or simply offer more robust and properly tested solutions to your end users. Surely, the enhancements are not going to stop here, so make sure to keep an eye on future releases.
What is the Setup functionality or page you find yourself using most? Don’t forget to share in the comments below!