> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/tutorials/guides/how-to-use-drafts.md).

# How to use Drafts

Drafts let you prepare changes to products, variant groups and variants without touching the current data, and merge them after review.

### What are drafts?

A draft is a named set of changes to a product, variant group or variant. You edit a draft in the normal editor, but the current data is not changed until the draft is merged. A product can have several drafts at once, and each can be sent to a colleague for review.

Read [Drafts](/fundamental-concepts/drafts.md) for an overview of statuses, review and conflicts.

To create and edit drafts you need the **Edit drafts** permission. To accept or reject changes you need the **Decide the outcome of drafts** permission and permission to edit the products, variant groups or variants concerned.

### Guides covering Drafts

* [How to create and edit a draft](/tutorials/guides/how-to-use-drafts/how-to-create-and-edit-a-draft.md)
* [How to send a draft for review](/tutorials/guides/how-to-use-drafts/how-to-send-a-draft-for-review.md)
* [How to review and merge drafts](/tutorials/guides/how-to-use-drafts/how-to-review-and-merge-drafts.md)

Drafts from suppliers are reviewed the same way. See [How to review supplier changes](/tutorials/guides/how-to-use-the-data-onboarding-portal/how-to-review-supplier-changes.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.struct.com/tutorials/guides/how-to-use-drafts.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.