> For the complete documentation index, see [llms.txt](https://help.besmart.software/t4i/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.besmart.software/t4i/quick-start-guide/easy-document-publishing.md).

# Easy Document Publishing

{% hint style="success" %}
With T4I, document publishing is just one click away. You can publish the documentation in PDF (drawings), DXF (drawings, sheet metal flat patterns – also from assemblies), DWG (drawings), and STEP (parts and assemblies).
{% endhint %}

## Publishing workflow example

1. Open the document you want to publish – part file, assembly, or a drawing.
2. Use one of the export commands on Be.Smart T4I (ribbon) -> Publish (panel).<br>

   <figure><img src="/files/Ydlr7Vg3S7FhlIErwd2Y" alt=""><figcaption></figcaption></figure>
3. You will be notified in the top right corner of the Inventor window the publishing was done.<br>

   <figure><img src="/files/pGXYcHWUgKOQmy0QTcGm" alt=""><figcaption></figcaption></figure>
4. Right-mouse-click the file name in the model/drawing browser tree and select the “Open File Location” command.
5. The default published file location is in subfolders named according to the published file type.<br>

   <figure><img src="/files/cPsDOhQSG2fiq1R0RyAn" alt="" width="252"><figcaption></figcaption></figure>

## Publishing settings

Publishing settings can be changed in Be.Smart T4I (ribbon) -> Be.Smart T4I (panel) -> Edit settings -> Publisher tab.

To change the published file location, the relative paths (see [Saving files using relative paths](/t4i/commands-overview/be.smart-t4i/edit-settings/publisher/saving-files-using-relative-paths.md)) can be used. Also, if you need a better configuration of your exported DWG, DXF, or DXF 3D (flat patterns) files, you need to provide your own customized INI file.


---

# 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://help.besmart.software/t4i/quick-start-guide/easy-document-publishing.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.