> 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/commands-overview/model/publish-imates.md).
# Publish iMates
## Command Description
This command, on the assembly level, creates copies of iMates from the individual parts contained in the assembly. Therefore it is possible to connect to iMates that otherwise would be located deeper in the assembly/subassembly structure (thus of no use for the iMates connections).
iMates publishing direction
## Command Location
* Assembly environment
## Command Settings
This command has no settings.
## Workflow Overview
1. Open the (sub)assembly with the component containing iMate(s).
2. Run the command and click the Select component button.
3. Select the component containing iMate(s).
4. Confirm the selection with the OK button.
5. In the parent assembly, insert the component with the second half of the iMate.
{% hint style="warning" %}
Do not use the in-place editing mode to publish iMates (i.e., do not publish iMates when in-place editing the subassembly within the main assembly), iMates would be published directly up to the parent assembly.
{% endhint %}
## Example of Using the Publish iMates Command
Example of using the Publish iMates command
---
# 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://help.besmart.software/t4i/commands-overview/model/publish-imates.md?ask=&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.
