> 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/push-parameters.md).
# Push parameters
## Command Description
This command creates copies of all user parameters of the active assembly in all child components. The command creates either new parameters or overwrites the current parameters with the same name. Read-only files are excluded.
Using this feature, all assembly components can be updated/driven from one place - from the main assembly. This feature can be used as an alternative to adaptivity or linking parameters using iLogic.
Push parameters command principle
## Command Location
* Assembly environment
## Command Settings
This command has no settings.
## Workflow Overview
1. Create parameters in the main assembly.
2. Run the command.
3. Select the parameters you want to push to child components.
## Example of Using the Push Parameters Command
Using of the Push parameters 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/push-parameters.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.
