# IdeasSettings Metadata Type in SFDX

> IdeasSettings configures Salesforce Ideas and Experience Cloud co-innovation portals, including voting, reputation, and multi-language support.

- Source: https://sfdxtalk.com/docs/metadata/ideas-settings-metadata-type/
- Category: Metadata
- Applies to: Salesforce Winter '27 (API version 68.0)
- Level: intermediate
- Published: 2026-11-12
- Last updated: 2026-11-12
- Publisher: SFDX Talk Editorial (unofficial; not affiliated with or endorsed by Salesforce)
- License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

## Architectural Overview

`IdeasSettings` governs the configuration of Salesforce Ideas, a collaborative innovation platform used internally and across Experience Cloud communities. Ideas enables employees, partners, and customers to submit suggestions, vote, comment, and track implementation statuses.

In enterprise architecture, `IdeasSettings` activates the underlying `Idea` and `IdeaTheme` data models, configures reputation score thresholds, and enables multi-language idea portals. Deploying these settings reliably ensures that customer-facing communities initialize with consistent voting rules and moderation guardrails.

```mermaid
flowchart TD
    A["Ideas.settings-meta.xml"] --> B["enableIdeas = true"]
    A --> C["enableIdeaThemes = true"]
    A --> D["enableIdeasReputation = true"]
    B --> E["Provisions Idea and Community Zones"]
    C --> F["Provisions IdeaTheme Object"]
    D --> G["Reputation Scoring and Badges"]
```

## Directory and File Conventions

`IdeasSettings` is stored in the standard `settings` directory:

| Property | Value |
| :--- | :--- |
| **Metadata Type Name** | `Settings` (member: `Ideas`) |
| **SFDX Directory** | `force-app/main/default/settings/` |
| **File Name** | `Ideas.settings-meta.xml` |
| **Scratch Org Key** | `ideasSettings` |

## Key Metadata Fields

The `IdeasSettings` XML schema defines community innovation parameters:

| Field Name | Type | Required | Description |
| :--- | :--- | :--- | :--- |
| `enableIdeas` | `boolean` | No | Master toggle that enables Salesforce Ideas across the org. |
| `enableIdeaThemes` | `boolean` | No | Enables Idea Themes to organize ideas around specific business initiatives. |
| `enableIdeasReputation` | `boolean` | No | Enables user points, levels, and reputation badges for community participation. |
| `enableMultiLanguageIdeas` | `boolean` | No | Allows users to submit and filter ideas across localized languages. |

> [!NOTE]
> Enabling Ideas provisions the standard `Idea` object. Custom fields, record types, and validation rules on `Idea` depend on `enableIdeas` being true.

## Declarative XML and Package Manifest Examples

Below is a production `Ideas.settings-meta.xml` configuration:

```xml title="force-app/main/default/settings/Ideas.settings-meta.xml"
<?xml version="1.0" encoding="UTF-8"?>
<IdeasSettings xmlns="http://soap.sforce.com/2006/04/metadata">
    <enableIdeas>true</enableIdeas>
    <enableIdeasReputation>true</enableIdeasReputation>
    <enableIdeaThemes>true</enableIdeaThemes>
    <enableMultiLanguageIdeas>false</enableMultiLanguageIdeas>
</IdeasSettings>
```

### Scratch Org Definition (`config/project-scratch-def.json`)

```json title="config/project-scratch-def.json"
{
  "orgName": "Ideas and Innovation Scratch Org",
  "edition": "Enterprise",
  "features": ["Ideas"],
  "settings": {
    "ideasSettings": {
      "enableIdeas": true,
      "enableIdeaThemes": true,
      "enableIdeasReputation": true
    }
  }
}
```

### Package Manifest (`package.xml`)

```xml title="manifest/package.xml"
<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>Ideas</members>
        <name>Settings</name>
    </types>
    <version>68.0</version>
</Package>
```

## Retrieval and Deployment via SF CLI

Retrieve and deploy settings via Salesforce CLI:

```bash
# Retrieve Ideas settings
sf project retrieve start --metadata "Settings:Ideas"

# Deploy Ideas settings to scratch org or sandbox
sf project deploy start --metadata "Settings:Ideas" --target-org dev-sandbox
```

> [!TIP]
> Always deploy `IdeasSettings` before deploying custom fields on the `Idea` object or Apex triggers referencing `Idea`.

## Senior Architect Best Practices and Gotchas

- **Build Sequencing**: Custom code or permission sets referencing `IdeaComment` or `IdeaTheme` will throw compile errors if `IdeasSettings` is not deployed first.
- **Experience Cloud Integration**: After enabling Ideas in settings, assign members to specific Community Zones via data seeding or setup automation.
- **Spam Mitigation**: When enabling Ideas in public-facing communities, implement reCAPTCHA and moderation rules to prevent automated spam generation.

## Frequently Asked Questions

### What features are governed by IdeasSettings?

IdeasSettings controls Ideas communities, voting algorithms, reputation levels, and idea themes.

### Where is IdeasSettings stored in source format?

It is stored in force-app/main/default/settings/Ideas.settings-meta.xml under the Settings type.

### What happens when enableIdeas is enabled?

Salesforce provisions standard Idea objects, community zones, voting triggers, and reputation metrics.

### Can ideas be deployed in scratch orgs?

Yes, by adding the Ideas feature to project-scratch-def.json and configuring the ideasSettings block.

## Official References

- https://developer.salesforce.com/docs/platform/api-metadata/references/meta-types/metadata-ideassettings.md