> For the complete documentation index, see [llms.txt](https://docs.durohub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.durohub.com/core-concepts/documents.md).

# Documents

Learn how to manage technical documentation and files through the Duro API.

### Document Types

Duro supports various document types:

* CAD Files
* Technical Drawings
* Specifications
* Test Reports
* Quality Documentation

### Querying Documents

Here's how to fetch documents:

```graphql
query {
  documents(first: 10) {
    edges {
      node {
        id
        title
        fileType
        version
        createdAt
        createdBy {
          name
        }
      }
    }
  }
}
```

### Document Operations

```graphql
mutation {
  createDocument(input: {
    title: "Assembly Instructions"
    componentId: "comp_123"
    fileUrl: "https://example.com/file.pdf"
  }) {
    document {
      id
      title
    }
  }
}
```

### File Management

* Direct upload URLs
* Version control
* Access permissions
* File metadata

***

## Documents on Change Orders

Documents can be attached to change orders as supporting reference material. See [Attaching Documents to a Change Order](/core-concepts/change-orders.md#attaching-documents-to-a-change-order) for usage.

### Querying Documents on a Change Order

```graphql
query GetCODocuments {
  changeOrders {
    get(filter: { ids: ["123e4567-e89b-12d3-a456-426614174000"] }) {
      connection {
        edges {
          node {
            id
            name
            documents {
              id
              componentId
              componentVersion
            }
          }
        }
      }
    }
  }
}
```

### Next Steps

Learn about managing product changes with [Change Orders](/core-concepts/change-orders.md).


---

# 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.durohub.com/core-concepts/documents.md?ask=<question>&goal=<endgoal>
```

`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.