Custom Settings Limits and Considerations

• Custom settings are a type of custom object. Each custom setting counts against the total number of custom objects available for your organization.
• The total amount of cached data allowed for your org is the lesser of these two values.
  • 20 MB
  • 2 MB multiplied by the number of full-featured user licenses in your org

  For example, if your org has three full licenses, you have 6 MB of custom setting storage. If your org has 20 full licenses, you have 20 MB of storage.

  Each certified managed package gets a separate limit in addition to your org limit. Each certified managed package gets the same limit as the org, based on the number of licenses up to 20 MB. For example, let’s say your org has two certified managed packages installed and you have three full licenses. Each certified managed package can have 6 MB of custom setting storage in addition to your org’s 6-MB custom setting storage limit.

  The org custom setting limits and certified managed package custom setting limits aren’t shared.

  • Custom settings that are added to an org via a certified managed package count against that package’s storage limit.
  • Custom settings that are added to an org directly or from a non-certified managed package count against the org’s storage limit.
  Using the previous example, if you have three full licenses, one non-certified managed package, and two certified managed packages, your custom settings storage limits are: 6 MB combined for the org and non-certified managed package, and 6 MB for each certified managed package.
• You can add up to 300 fields per custom setting, unless your field limit for custom objects is lower than 300. If your custom objects field limit is lower than 300, your field limit for custom settings is equal to your custom objects field limit.
• You can’t share a custom setting object or record.
• No owner is assigned when a custom setting is created, so the owner can’t be changed.
• Accessing an undeleted custom setting in a formula field results in an error if the user doesn’t have the “Customize Application” permission. To prevent this error, redeploy this custom setting to the organization. Alternatively, delete this custom setting, re-create it with the same name and data, and then delete and re-create all formula fields that use this setting.
• If a cross-object formula references a currency field from a custom setting, this field value isn’t converted to the currency of the record containing the formula. An inaccurate formula result is possible if the custom setting field’s currency and the record's currency are different.
• You can’t disable specific permissions with a muting permission set.

To see how much custom settings data your organization is using, from Setup, enter Custom Settings in the Quick Find box, then select Custom Settings. For each custom setting, this page lists the size of one record, the number of records created, and the total size used for each custom setting.

Record size is based on the maximum field size of each field type, not the actual storage that’s used in each field. When adding fields to a custom setting definition, use the appropriate type and specify a length that doesn’t exceed what’s needed for your data. This action helps you avoid reaching the cached data limit. For example, if you create a US social security number (SSN) field, select the Text data type and specify a length of 9. If you select a Text Area data type, the field would add 255 characters to the usage count for each record, regardless of the number of characters entered.

Note A icon indicates that the custom setting is in an installed managed package. You can’t edit or delete a protected custom setting installed from a managed package.