> For the complete documentation index, see [llms.txt](https://docs.bimcat.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bimcat.org/user-manual/usage/library-browser/library/add-to-project.md).
# Add to Project
The **Add to Project** button becomes available when one or more items are checked using the checkboxes.
Allows to add the checked family types to the current Revit project. They will be added together with their corresponding bimCAT back annotations, that will be used to restore the bimCAT collections, builders and bimCAT-specific material layers during the next bimCAT export.
* The **loadable** family types (Doors, Windows, Columns, etc.) are added to the Revit project together with their whole family. Even if you check only a single family type from a family containing multiple types, the complete family will be imported to the project anyway.
* The **system** family types (Walls, Ceilings, Floors, etc.) are added to the Revit project as separate entities, without importing their whole library.
After the family types are added to the project, they instantly become visible in the Current Project tab.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.bimcat.org/user-manual/usage/library-browser/library/add-to-project.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.