> For the complete documentation index, see [llms.txt](https://community.threekit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.threekit.com/platform-documentation/project-data/logic/conditions.md).

# Conditions

Conditions are available inside both PartReference attributes, as well as Rules.

PartReference attribute conditions serve as a tag-filter. They are available as both explicit AND (&) or as implicit ALSO.

<figure><img src="https://2668731230-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fknvt0jlDBXmk91mWaWXB%2Fuploads%2FDs62iej0gcVwcYwYMtuu%2FConditions_1.png?alt=media&amp;token=c862c691-8660-47ba-ba12-c5e57a6837ef" alt=""><figcaption></figcaption></figure>

Rule Conditions are only available as a direct comparison of value.

**All listed conditions inside a rule must be met, for the actions to execute.**

The only event trigger available in the UI is for an attribute having changed its value.

There is currently no way to compound multiple conditions with OR, or combinations of OR and AND. ELSE and ELSE IF are not currently available either.

The available conditions are context-sensitive, depending on the type of attribute being used for comparison.

### Conditions List

1. **Attribute has changed** - event triggered when the attribute’s value has changed, typically by the front end user
2. Attribute **is any of / is none of** listed values (applicable only to  Item or Asset types)
3. Attribute’s Item or Asset has the given **metadata key=value** pairs (applicable only to  Item or Asset types)
4. Attribute **= or !=** listed value (applicable only to  Number, String, Boolean, and Color types)
5. Number Attribute **>, >=, <, <=** listed value
6. String Attribute Value **Includes or Doesn’t Include** listed String
7. **Layer** - Check if Listed Layer Name inside the Listed Composite Asset is currently being rendered


---

# 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://community.threekit.com/platform-documentation/project-data/logic/conditions.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.