> For the complete documentation index, see [llms.txt](https://docs.realmacsoftware.com/elements-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmacsoftware.com/elements-docs/elements-language/component/properties-json/general-structure/enabled.md).

# Enable

Enable and disable controls based on another control's value.

The `enable` key in an object's properties can be set using a logical expression that evaluates to `true` or `false`. This determines whether a specific UI element is enabled or disabled based on the conditions specified in the expression. Works in the same way as [visible](/elements-docs/elements-language/component/properties-json/general-structure/visible.md).

* **Boolean Logic**: Use logical operators (`&&`, `||`) to combine multiple conditions.
* **Comparison Operators**: Use `==`, `!=`, `>`, `<`, `>=`, `<=` to compare values.

## Examples

1. **Complex Condition**

   ```json
   "enable": "(buttonStyle == 'filled' || buttonStyle == 'outline') && showIcon == true"
   ```

   This makes the control enabled only when a button style is chosen and icons are enabled.
2. **Enabled Based on Numeric Ranges**

   ```json
   "enable": "imageBlur > 0 && imageBlur <= 20"
   ```

   Useful for enabling fine-tuning controls only when blur is active.
3. **Negation to Disable**

   ```json
   "enable": "useCustomColors != true"
   ```

   The property is enabled when `useCustomColors` is `false`.

## Disabled

The `disabled` key is the inverse shorthand: instead of an expression, it takes an object with an `id` and a `value`. The control is disabled whenever the referenced property equals the given value.

```json
{
  "title": "Text Shadow",
  "id": "textShadow",
  "disabled": {
    "id": "bgType",
    "value": "image"
  },
  "themeShadow": {
    "mode": "text",
    "default": {
      "name": "none"
    }
  }
}
```

In this example the Text Shadow control is greyed out while the `bgType` property is set to `image`.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.realmacsoftware.com/elements-docs/elements-language/component/properties-json/general-structure/enabled.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.