> 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/be.smart-t4i/edit-settings/auto-iproperties/synchronization-of-iproperties.md).

# Synchronization of iProperties

## Workflow overview (Automatic synchronization)

On the tab *Synchronize,* select iProperties to be synchronized between the model and drawing, and select the synchronization direction (from/to Model to/from Drawing). *On Open* means the iProperties are synchronized from the model to the drawing when the drawing is opened, whereas *On Save* means the model properties are updated after saving the drawing.

The Filter button at the bottom left corner of the window helps you to sort out the available properties into more convenient categories, like *Summary*-related, *Project*-related, or file *Status*-related. By default, this filter is turned on (the button is bluish). After disabling the filter, the properties are sorted differently into the following categories: (general) *Summary Information*, *Document Summary Information*, and *Design Tracking Properties*.

<figure><img src="https://4060565498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL8qMZuBhZUXGRVospdct%2Fuploads%2FSfqX8ZsQhaITDt6tZj3W%2Fimage.png?alt=media&amp;token=92a09026-b187-4e4e-80f4-869d35907c28" alt=""><figcaption><p>iProperties to be synced </p></figcaption></figure>

Workflow example

Given the specific settings depicted in the image above, two iProperties (Description and Authority) will be updated upon opening the drawing file based on the changes in the model file.

Workflow overview (Manual synchronization)

<figure><img src="https://4060565498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL8qMZuBhZUXGRVospdct%2Fuploads%2Fa5UKSSLxwNnrXiCU3wE3%2FSynchronization%20of%20iProperties.gif?alt=media&amp;token=197146a0-a84f-4bbb-ae0e-43ff97533263" alt=""><figcaption><p>Example of automatic iProperties synchronization</p></figcaption></figure>

Moreover, changes to the iProperties of the model/drawing can be immediately projected to the respective file without waiting for the "automatic event" (e.g. opening the drawing). In such a case, *Model to Drawing* or *Drawing to Model* commands from `Be.Smart T4I -> iProperties Transfer` can be used.

See more information in [iProperties Transfer](/t4i/commands-overview/iproperties-transfer.md) section.

<figure><img src="https://4060565498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL8qMZuBhZUXGRVospdct%2Fuploads%2FJHBKxS7hvn6EPojDBCOk%2Fimage.png?alt=media&amp;token=2ac4e8ba-3697-43d2-b365-e5950f76c86f" alt=""><figcaption><p>Manual iProperties transfer</p></figcaption></figure>


---

# 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/be.smart-t4i/edit-settings/auto-iproperties/synchronization-of-iproperties.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.