> For the complete documentation index, see [llms.txt](https://help.craftsmanplus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.craftsmanplus.com/play/properties/dynamic-content/adding-dynamic-content-to-a-layer.md).

# Adding Dynamic Content to a Layer

Dynamic Content is enabled per layer from the properties panel.

***

### Enabling the Module

{% stepper %}
{% step %}

### Select the layer you want to make dynamic

{% endstep %}

{% step %}

### **In the properties panel, expand the layer's Title Section by clicking the layer name area.**

{% endstep %}

{% step %}

### **Turn on the Dynamic Content toggle. The condition popup opens automatically.**

Once conditions are set, the module displays a summary of the layer's conditions next to the toggle, so you can see how a layer is configured at a glance.
{% endstep %}
{% endstepper %}

***

### Setting Conditions

In the popup, click the "+" button and choose a condition category from the menu, then check the options the layer should display for.

* Selecting multiple options within a category means the layer displays when **any** of them match. For example, checking both Saturday and Sunday shows the layer on weekends.
* Click the **+** button again to add a second condition category. When a layer has two categories, **both** must match for the layer to display. For example, Android + Monday only shows the layer to Android users on Mondays.

A layer supports a maximum of **two** condition categories, and the same category cannot be added twice. Categories already in use are unavailable when adding a second condition.

For every option available in each category, see [Conditions](https://help.craftsmanplus.com/play/properties/dynamic-content/conditions.md).

{% hint style="info" %}
*If no layer in the project matches the viewer's conditions, nothing displays unless a* ***Fallback*** *is configured. It's strongly recommended to set one. See* [*Fallback*](https://help.craftsmanplus.com/play/properties/dynamic-content/fallback.md)*.*
{% endhint %}

***

### Identifying Dynamic Layers

Layers with Dynamic Content enabled display a **dynamic icon** in the layers panel. Hover over the icon to see a tooltip listing the layer's conditions.

***

### Removing Dynamic Content

Turn the **Dynamic Content** toggle off to remove the dynamic behavior. The layer returns to being a regular layer that always displays. Your condition selections are cleared, so re-enabling the toggle starts fresh.

***

### Where Dynamic Content is Available

Dynamic Content works on standard layers, layers inside groups, global layers, and custom layers added inside components like Scrollable and Carousel.

It is not available on the default layers that come built into games and components, or in Animated Banner projects.


---

# 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://help.craftsmanplus.com/play/properties/dynamic-content/adding-dynamic-content-to-a-layer.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.
