> 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/design/explanation/project-and-component-settings.md).

# Project and Component Settings

## Load Settings

Load Settings are used to generate the set of Load Cases for which the component should be analyzed. They will typically be set at the Project level, and components will inherit those settings. An individual component's load settings can be modified where they differ from the rest of the project.

Certain load settings like Wind, Roof Live, and Dead are only available for Roof Components, while others, like Floor Live and Dead, are only available for Floor Components. Those settings will only affect components of the corresponding type.

## Analysis Settings

Analysis Settings can affect the parameters used in analysis checks. Examples include deflection limits, repetitive member increase factor, and chord bracing settings.

## Material Settings

Material Settings are the lists of materials available for designing and the default material for each member type. Each component has a list of lumber and a list of plates, which will affect things like what materials are considered during Upgrade and Analyze and the material you can manually choose for existing members and plates. Materials are set up and managed in the [Materials App](https://materials.paragontruss.com).

## Feature Pattern Settings

Feature Pattern Settings allow you to specify defaults to use when creating new Feature Pattern Trusses from scratch within Design mode. Refer to the [Feature Pattern Settings](https://docs.paragontruss.com/design/getting-started/interface-overview.md) topic for more information.

## Default Profile Settings

Default Profile Settings allow you to define default properties used when creating new components from scratch within Design mode. Refer to the [Default Profile Settings](https://docs.paragontruss.com/design/getting-started/interface-overview/header.md#default-profile-settings) topic for more information.

## Project vs. Component Settings

The above settings can be set for a single component or an entire project. Any settings made at the component level will override any project-level settings for that specific component. Project settings are accessed via the [`Project Settings`](https://docs.paragontruss.com/design/getting-started/interface-overview/header.md#project-settings) button in the [`Header`](https://docs.paragontruss.com/design/getting-started/interface-overview/header.md) and component settings are accessed via the [`Truss Settings`](https://docs.paragontruss.com/design/getting-started/interface-overview/actions-toolbar.md#truss-settings) button in the [`Action Toolbar`](https://docs.paragontruss.com/design/getting-started/interface-overview/actions-toolbar.md) .

{% hint style="info" %}
Note

Use [Materials](https://docs.paragontruss.com/materials/) to manage your material lists.
{% 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://docs.paragontruss.com/design/explanation/project-and-component-settings.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.
