> 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/linking-a-catalogue-to-a-project.md).

# Linking A Catalogue to a Project

Linking a catalogue to a project connects your playable to the catalogue's dataset.\
Once linked, the project becomes **data-aware**, meaning the creative’s layers can update automatically.

<figure><img src="https://3019081569-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZBycFFNxrdS0X9OsGtmT%2Fuploads%2Fgit-blob-645fa90d07f453d7ca0ba837de27a672dfdf4bc8%2Fimage-20251112-200607.png?alt=media" alt=""><figcaption></figcaption></figure>

### **How to Link a Catalogue:** <a href="#how-to-link-a-catalogue" id="how-to-link-a-catalogue"></a>

Follow these steps to connect a project to a catalogue. You can connect multiple projects to one catalogue.

{% stepper %}
{% step %}

### **Open your project in CRAFTSMAN PLAY**

This will be the project you conect the catalogue to.
{% endstep %}

{% step %}

### **Navigate to Project Settings**

Click the gear icon in the top right corner of the project.
{% endstep %}

{% step %}

### **Enable the “Link Catalogue” toggle, then click on “Select Catalogue”**

A list of all available catalogues from your Studio workspace will appear.
{% endstep %}

{% step %}

### **Select the Catalogue you want to connect**

Then, select the conditions you want the project to use from the catalogue:
{% endstep %}
{% endstepper %}


---

# 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/linking-a-catalogue-to-a-project.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.
