> 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.md). # Connecting Your Project Link a CRAFTSMAN PLAY project (new or existing) to an external catalogue so published data updates flow to all connected projects. The **Catalogue system** operates independently from individual projects in CRAFTSMAN PLAY.\ A catalogue is not embedded within a single project, it exists as a separate data source that can be linked to multiple projects. This separation allows a single catalogue to power many projects at once, ensuring that updates made to the catalogue are automatically reflected in every connected project after publishing. *For example, a single language-based catalogue could manage button translations for multiple campaigns.* Catalogues also work seamlessly with **projects created before the Catalogue feature was released**.\ Any existing playable can be linked to a catalogue at any time by opening the project’s settings and enabling the Catalogue connection. Once linked, its layers can be mapped to catalogue columns the same way as new projects, **no migration required.** --- # 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.md?ask=&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.