> For the complete documentation index, see [llms.txt](https://docs.paragontruss.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.paragontruss.com/projects/reference.md).
# Reference
## Project
A Project is comprised of layouts, components, and associated project files that will help you manage workflow through design, sealing, and production.
## Project Properties
Project Properties include a combination of required and optional fields. Some of the fields are auto-populated. All of the fields are editable, except `Created At` and `Organization` .
### Required and Auto-populated Project Properties
* **Name** - The name used to refer to the Project—on sealed drawings, for example
* **Created At** - This field is automatically populated when a project is created
* **Organization** - The organization which the project is associated (typically your company)
* **Design Code** - The Project's building code and TPI version (required when requesting component review or repairs)
* **Contact Info.** - Contains the contact information of the user who created the Project by default. The fields will appear in the properties of the Job created in Review when you Request Seals or Repair.
* Contact Name
* Contact Phone
* Contact Email
### Optional Project Properties
Fields that appear on the cover page for your Seal or Repair Job. They will be applied to Jobs you create from the Project in [Paragon Review](https://review.paragontruss.com/).
* **Region** - The region in which the Project is being built/sealed (State or District)
* **Customer Info.**
* Customer Name
* Lot Number
* Address
* City
* Subdivision
* Model
* **Building Designer Info.**
* Building Designer Name
* Building Designer Address
* Building Designer City
* Building Designer State
* Building Designer License Number
* **Project Salesman**
---
# 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.paragontruss.com/projects/reference.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.