> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/order-processing/purchase-order/po-configuration/do-not-allow-printing-of-un-approved-documents.md).

# Do not allow printing of Un-Approved Documents

**YouTube:** [How to Restrict Printing of Unapproved Purchase Orders?](https://youtu.be/akAFTPxj9LU)

## How to Restrict Printing of Unapproved Purchase Orders?

This tutorial explains how to restrict the printing of **Un-Approved Purchase Orders** in Logic ERP. This feature ensures that only approved Purchase Orders can be previewed or printed, helping maintain authorization control and preventing unauthorized document circulation.

***

### **Objective of This Feature**

* Prevent printing of un-approved Purchase Orders
* Ensure approval before document printing
* Improve authorization and process control
* Avoid accidental or unauthorized printing

***

#### **Access to the Purchase Order Configuration**

* Open **Purchase Order Configuration Window**
* Navigate to **Print Options**
* Locate and enable the option labeled as:

> **“Do not allow printing of Un-Approved Documents”**

<figure><img src="/files/zg5rTXR6lIwS6bW86T36" alt=""><figcaption></figcaption></figure>

* Click **Save**

***

### **Verify Purchase Order**

**Transaction Process**

* Create a **New Purchase Order**
* Proceed to the **Item Details Section**
* Enter the required items

**Attempt Printing Before Approval**

* Click on the **Print Button** before approval

<figure><img src="/files/GgqtjgAOpQWyVPFZ6EzR" alt=""><figcaption></figcaption></figure>

**System Behavior**

* Software restricts the action
* Displays error message stating:

> *"*&#x53;ave the document before printing.. Only approved documents are allowed Printing.*"*

* Save the Purchase Order entry

***

### **Approve the Purchase Order**

**Approval Process**

* Select the saved Purchase Order entry
* Right-click on the entry
* Click on:
  * **Approve Event Option**

<figure><img src="/files/BinG7rOcrbZIJYg61bHk" alt=""><figcaption></figcaption></figure>

**Confirmation**

* Click **Yes** to approve the document

***

### **Print Approved Purchase Order**

**Verification Process**

* Open the approved Purchase Order in **Modify Mode**
* Click on **Print**

<figure><img src="/files/heFzSC2ENCp6hb8DhAnq" alt=""><figcaption></figcaption></figure>

**System Behavior**

* Software allows:
  * Print Preview
  * Successful Printing of the Purchase Order

***

### **Key Benefits**

* Ensures only authorized documents are printed
* Strengthens approval workflow control
* Prevents accidental printing of pending documents
* Improves document security and compliance

***

### **Best Practice Tips**

* Assign approval rights only to authorized users
* Ensure Purchase Orders are verified before approval
* Use approval workflows for better procurement control

***

### **Final Outcome**

* Un-approved Purchase Orders cannot be printed
* Only approved documents are allowed for printing
* Improved authorization and document control
* Better compliance and operational security


---

# 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://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/order-processing/purchase-order/po-configuration/do-not-allow-printing-of-un-approved-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.
