Skip to main content
New tool CRON Expression Builder — preview next run times before you schedule Apex. Open the builder →
Diagram showing how to enable list custom settings access using Salesforce permissions
Admin

How to Enable List Custom Settings and Fix Missing Options

Ever wonder why the New button is missing on the Custom Settings page? It usually comes down to one system permission you need to toggle. Here is how to fix it with a profile or a permission set.

The short answer

If the New button or other options are missing on custom settings, assign the Customize Application system permission through a permission set or profile. The user also needs the View Setup and Configuration permission to reach Setup.

Key takeaways Assign the Customize Application system permission through a permission set or profile so the New button appears on custom settings. Check that the user also has View Setup and Configuration, or they cannot open the Setup interface at all. Grant Modify Metadata Through Metadata API to deploy or edit custom settings from developer tools and APIs. Do a hard browser refresh or log out and back in if the options do not appear right after a permission change. Check whether a custom setting belongs to a managed package namespace, since protected package settings cannot be edited.

Why you need to enable list custom settings

Ever found yourself staring at the Custom Settings page, wondering why the "New" button is playing hide-and-seek? You're trying to enable list custom settings for a project, but the option is just gone. I've seen this happen to plenty of experienced admins who are moving into a new org and realize their permissions aren't what they thought.

You're likely missing the Customize Application system permission. Salesforce treats Custom Settings as part of the core application schema, so it doesn't let just anyone poke around in there. If you don't have that specific permission, the UI simply hides the creation and management options from you.

There is more to it than clicking a checkbox. You need to understand where this fits into your security model, and if you're still getting comfortable with how permissions are layered, it's helpful to review the basics of Salesforce roles vs profiles to see how these system-level rights are handed out.

A realistic mockup of the Salesforce Setup interface showing various administrative toggle switches and configuration settings.

A realistic mockup of the Salesforce Setup interface showing various administrative toggle switches and configuration settings.

Steps to enable list custom settings on a profile

If you're the one in charge of the org, you'll need to update your profile (or whichever profile needs access). Most of the time, I prefer using a Permission Set for this because it's cleaner, but sometimes a profile change is just faster for a quick fix in a sandbox.

  1. Head over to Setup and type Profiles in the Quick Find box.
  2. Select the profile you want to edit.
  3. Find the System Permissions section.
  4. Click Edit and look for Customize Application.
  5. Check the box, hit Save, and you're good to go.

Once you do this, the "New" button should appear, and that is all it takes. Just keep in mind that this permission is powerful. It lets users change almost anything in the Setup menu, so don't hand it out like candy.

Using a Permission Set for better control

In my experience, the best way to handle this is through a Permission Set, which is much safer than modifying a standard profile. You can create a "Metadata Manager" set, add the Customize Application permission there, and then assign it only when someone actually needs to create custom settings or modify objects. It keeps your security tight and your auditors happy.

Troubleshooting the missing "New" button

So you've enabled the permission but you still can't see the option? I've run into this a few times. First, make sure you also have the View Setup and Configuration permission. Without that, you can't even get into the room, let alone sit at the table.

Another thing that trips people up is the browser cache. Salesforce is notorious for hanging onto old UI states, so give it a hard refresh or log out and back in. If you are working in a sandbox that was recently refreshed, double-check that your user permissions actually carried over correctly.

One thing I always tell my team: if you're working with Managed Packages, some Custom Settings are "protected." You won't be able to edit those even with the right permissions because the package developer has locked them down. Always check if the setting belongs to a namespace before you start pulling your hair out.

If you're a developer using tools like VS Code or the Metadata API, you might need one more thing. Make sure your user has the Modify Metadata Through Metadata API permission. It's a separate beast from the UI permission but just as vital for modern deployments.

Key takeaways

  • The Customize Application permission is the "master key" for this issue.
  • Use Permission Sets instead of Profile changes to keep your org secure.
  • You must also have View Setup and Configuration enabled to see the menu.
  • Refresh your browser cache if the "New" button doesn't show up immediately.
  • To create list custom settings via API, make sure your metadata permissions are active.

Salesforce permissions can be a bit of a maze, but once you know which toggle to flip, it's a five-minute fix. Just remember to be careful with "Customize Application" since it opens up a lot of doors. If you're looking for more ways to speed up your workflow, there are Salesforce chrome extensions that help you navigate the Setup menu faster.

Frequently asked questions

Why is the New button missing on Custom Settings in Salesforce?

The New button is hidden when your user account lacks the Customize Application system permission. You also need the View Setup and Configuration permission to reach the Setup menu.

How do you enable the Customize Application permission in Salesforce?

Go to Setup, open Profiles or create a Permission Set, find the System Permissions section, check Customize Application, and save your changes.

Why can't I edit a custom setting from a managed package?

Managed package developers can mark custom settings as protected, which locks them down. If a custom setting belongs to a namespace and is protected, no administrative permission will let you modify it.

What permissions are needed to deploy custom settings with the Metadata API?

Deploying custom settings through tools like VS Code or the Metadata API requires the Modify Metadata Through Metadata API permission.

Newsletter

One email every Tuesday

New guides, tool updates, and the release-note changes that break things.

No spam. Unsubscribe in one click.

Comments

Loading comments...

Leave a Comment