> 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/catalogue/connecting-your-project/selecting-conditions.md).

# Selecting Conditions

When you first link a catalogue, the project does **not automatically use all condition columns** from that catalogue.

Instead, you’ll choose which **conditions** should actively apply to this project.

1. In the same **Project Settings → Catalogue** panel, locate the list of available **Conditions**.
2. Check the boxes for the conditions you want this project to respond to, for example:
   * `Language`
   * `Device:System`
   * `Time:Month`
   * `Location:Region`
3. Only these selected conditions will be used to determine which catalogue row loads at runtime.
4. Unselected conditions are ignored, even if they exist in the catalogue.

This gives each project full control over how much contextual logic it uses.\
For instance, one project might only vary by *Language*, while another uses *Language + Weather + Time* together.

{% hint style="info" %}
**Note:** ALL selected conditions must match the user’s environment for that row to be used. If the user is in New Jersey & it is Sunny, a row with a “New Jersey” in a location column, but “Rainy” in a weather column will not be shown. **ALL conditions must match.**
{% endhint %}


---

# 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/catalogue/connecting-your-project/selecting-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.
