> For the complete documentation index, see [llms.txt](https://docs.diracinc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.diracinc.com/videos/tutorials/sequencing-requirements-and-animations/adding-requirements.md).

# Adding Requirements

{% embed url="<https://dirac-webflow-videos-cdn.b-cdn.net/gitbook-demo-videos/Adding%20Requirements%20(1).mp4>" %}

### What this allows you to do

Attach supporting information (i.e. tools, notes, and media) to instruction steps so operators have everything they need at the point of execution.

### Ways to Add Requirements

#### Requirements Library

* Accessed from the dashboard
* Create reusable requirements by selecting a type and entering details
* Requirements in the library can be used across multiple instructions and assemblies

#### Add Requirements Inline

* Add requirements directly from the **Requirements** tab on an instruction step
* Inline requirements are automatically saved to the library for future use

### Local vs Global Requirements

When adding a requirement, you’ll choose whether it is **local** or **global**.

* **Local requirements** apply only to the specific step where they are added
* **Global requirements** are associated with specific part geometry and are automatically applied whenever that component appears in an instruction

Global requirements help maintain consistency and preserve shared knowledge across your team.

### Key Tips

* Use global requirements for standard tools or recurring operations
* Use local requirements for step-specific guidance
