> For the complete documentation index, see [llms.txt](https://manual.firstresonance.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.firstresonance.io/features/procedures/part-procedure-relationship.md).
# Part-Procedure Relationship
Procedures may be associated with one or more parts to relate a workflow with a specific workpiece. Link a part and a procedure from the **Parts** tab on a procedure. Note that this isn't a parts list that are in an assembly - by setting this relationship you are telling ION which procedures are used to produce a certain part or assembly.
You can also set up the part-procedure relationship from the parts library sidebar.
When you link parts through this relation when you have the "Require part-procedure relationship to be approved" box checked in your organization settings, ION will not allow you to create runs unless the selected part is linked to the selected procedure.
With this box checked, when you attempt to create a run with a procedure that is not linked to the selected part, you will get an error that looks like this:
#### Required vs. Optional Part Procedure Relationships
When linking parts to an inspection procedure, the **Required** or **Optional** setting determines whether an inspection run is automatically created upon receipt.
* This toggle **ONLY** effects **INSPECTION** type procedures their parts upon receipt.
* **Required:** When a part marked as *required* is received, an inspection run is automatically generated for that part according to the associated procedure.
* **Optional:** When a part marked as *optional* is received, no inspection run is automatically created. You can still initiate an inspection manually if needed.
This setting helps control which parts must go through inspection by default and which can be inspected at your discretion. See it in action below.
{% embed url="" %}
---
# 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://manual.firstresonance.io/features/procedures/part-procedure-relationship.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.
