> For the complete documentation index, see [llms.txt](https://docs.atomyx.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.atomyx.io/atomyx-submit/implementation/submission-workflow/approval-workflow.md).

# Approval Workflow

This is where the customer, and in some cases internal staff, decide whether the file is ready to proceed.

### Internal approval

Files that pass cleanly may continue automatically.

Files that produce warnings or errors may be routed to internal prepress or DTP staff for review before they are released to the customer for approval or moved onward in the workflow.

This helps teams focus only on exception cases rather than reviewing every file manually.

### Customer approval

When the proof page is ready, the customer can review it and either:

* approve the submission
* reject the submission
* restart the cycle with a revised file, depending on the implementation

Approval may be presented through:

* the portal interface
* an approval link
* an email-driven review path that leads back into the portal

### What happens after approval

Once the customer approves:

* the order status can be updated
* processed files and proof references can be returned to the ERP or ordering platform
* the job can move into production planning and output

### What happens after rejection

If the customer rejects the proof:

* the order can be flagged for follow-up
* staff can be notified
* the customer may be invited to upload a replacement or corrected file

### Best practice

Make approval status changes explicit and traceable.

The workflow should make it clear:

* what was approved
* when it was approved
* which file version was approved
* what should happen next


---

# 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:

```
GET https://docs.atomyx.io/atomyx-submit/implementation/submission-workflow/approval-workflow.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.