> For the complete documentation index, see [llms.txt](https://docs.wem.io/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wem.io/platform/wemreference/keywords/concepts/concept.md).

# Concept

{% hint style="info" %}
The `Concept` keyword can be used to get a handle to a concept in a set while the set is being iterated. It can be used in a loop, a repeater or datagrid based on a concept-set as label within the repeater, or in where-filter expressions on a concept-set.

This function is NOT SQL compatible. For more information about SQL compatibility, see our [documentation](/platform/wemreference/sql-compatibility.md).
{% endhint %}

{% hint style="success" %}
Points to a (viariable) concept within a set to use as a handle while iterating through a set of concepts, so a certain action or check can be performed on each concept within the iteration. 
{% endhint %}

<details>

<summary><code>Concept</code></summary>

`GetChildren('Color') WHERE concept:'PrimaryColor' = true`\
*=> all children of the Color concept that have a property PrimaryColor set to true. The concept-keyword is used as a handle to check - while going through the Children of Color - each concept for its PrimaryColor property.*&#x20;

</details>


---

# 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.wem.io/platform/wemreference/keywords/concepts/concept.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.