> 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/materials/how-to/plate-lists.md).

# Create & Modify Plate Lists

## Create a Plate List

### Step 1 - Click the `+` button to begin creating a new plate list

### Step 2 - Enter a name for your custom list

{% hint style="success" %}
Tip

This custom name will be displayed in the Paragon Design interface when editing material settings.
{% endhint %}

### Step 3 - Add plates to the list by selecting or deselecting options in the grid

## Duplicate a Plate List

### Step 1: Choose the List you would like to copy

### Step 2: Click the `Duplicate` Button in the header

### Step 3: Edit the duplicated list

The list name will start with `Copy Of` and then the previous list name. For example, duplicating a Plate List with the name of `Example List` will result in a new list called `Copy of Example List`

{% hint style="info" %}
Note

From the Edit Plate List screen, you will have the option to rename the Set.
{% endhint %}

## Choose a Default List

### From the home screen right click on a list and choose Make Default

<figure><img src="https://89124082-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3EIU5QusPFpnkhDCIhAg%2Fuploads%2Fgit-blob-47b0406d16d56f7b4d0bceafe5fc05ca558fcc08%2Fset-default-plate-list.gif?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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/materials/how-to/plate-lists.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.
