> ## Documentation Index
> Fetch the complete documentation index at: https://docs.speckle.systems/llms.txt
> Use this file to discover all available pages before exploring further.
> ## Agent Instructions
> These docs contain multiple Speckle product experiences. For Speckle 2026.9, prefer /next/ pages for the topics and changes they cover. The navigation label Current does not override this version-specific precedence.
> Coverage under /next/ is incremental. Use Current documentation for unchanged topics and when a /next/ page says coverage is unavailable or explicitly refers you to Current. Do not infer a feature was removed from a missing page.
> Read the page-specific documentation status, applicability, affected guidance and replacement links in agent-only content. Impacted, changed and superseded apply only to the stated scope; they do not mean the entire feature is deprecated. Historical connector guides apply only to the legacy connector described.
> Match guidance to the customer's deployment version, model data format and connector. Respect plan, permission and compatibility restrictions. If an unknown version or data format changes the answer, ask a focused clarification; do not infer deployment version from the date alone.
# Update parameters from the model viewer
> In 2026.9 you batch-edit parameters in the Elements panel, then apply them in the connector via Issues.
Documentation set: Speckle 2026.9. Status: current. Authority: canonical for this version and the coverage on this page.
Applies to version 2026.9, from 2026-09; this is not a rollout date for every deployment.
Authoritative Speckle 2026.9 documentation for the topic covered here. For Speckle 2026.9, prefer this page over conflicting earlier guidance. Follow the linked pages in the other documentation version for unchanged topics and where this page says coverage is not yet available. Respect data-format, deployment, plan, permission, and compatibility limitations stated in the page.
This is 2026.9 documentation. Coverage here is incremental: a page exists only where 2026.9
differs or is newly documented. For any other topic, switch to **Current** (2026.8 and earlier) in
the version selector.
In 2026.9 you review and batch-edit model parameters from the **Elements** panel
in the model viewer, then apply those changes back in Revit, Rhino, or Civil3D.
Each batch is still logged as an Issue.
This page covers only what changed. For the dashboard-widget path from before 2026.9,
editable types, connector apply steps, and known limitations, see
[Parameter Updater](/beta/parameter-updater).
Parameter updates in 2026.9 run against models in the new data format. If a model has not moved
yet, follow [Speckle's data model is changing](/workspaces/data-model-migration).
## What changed
Before 2026.9, Parameter Updater is a **Data Conditioning** widget that you add to a
dashboard. In 2026.9 that widget is not the path: you work on the models already
open in the viewer.
* **Where you edit:** the **Elements** panel in the model viewer, not a dashboard
widget.
* **How you start:** open **Elements**, then choose **Update parameters**. You do
not drag a widget from Data Conditioning.
* **Which models you can edit:** models loaded in the viewer, not widget data
sources you pick separately.
* **New attributes:** open **Columns** and use **New attribute name…** while
update mode is on. There is no **+** button on the column headers.
* **What submit creates:** an Issue that stores the parameter changes. It does
not attach a 3D screenshot or viewer state the way the widget does before 2026.9.
Apply in the connector is unchanged: open the Issue on the model card and use
**Apply changes**. Connector version, host support, and the limits in
[Parameter Updater](/beta/parameter-updater) still apply.
## Example use cases
Use Parameter Updater when you know the values that model elements should carry
and want to set or standardise them in bulk. Common examples include:
* **Review and approval:** update an element's **Status** as work progresses, or
set an **Approval status** after a review.
* **Responsibility and coordination:** assign elements to a discipline, team,
owner, or coordination zone.
* **Delivery planning:** add a project phase, work package, milestone, or
installation sequence to selected elements.
* **Asset information:** add or correct asset IDs, system references, locations,
maintenance zones, or handover fields.
* **Quality checks:** fill missing required parameters or correct values found
during model review and validation.
* **Data standardisation:** replace inconsistent names, codes, or allowed values
with the agreed project terminology.
* **Known classification values:** apply an agreed classification code to a
selection when you already know which code is correct.
These are data-conditioning workflows: you are maintaining parameter values on
existing elements. Applying a known classification value is also data
conditioning. It becomes autoclassification when the system infers which
category or type an element belongs to.
## What you can change
With Parameter Updater, you can:
* add a new parameter;
* insert a value where an existing parameter is empty;
* overwrite an existing parameter value; or
* clear a parameter value.
You cannot delete a parameter. Clearing removes its value but leaves the
parameter on the element.
## Update parameters in 2026.9
Open the project and model in the Speckle web app so the 3D view loads. You should see the model
and the viewer panels, including **Elements** in the bottom dock.
If **Elements** is not showing, open it from the viewer panel switcher, or press Shift+T. You
should see a table of elements for the models in the scene.
In the Elements toolbar, choose **Update parameters** (pencil). Columns under `properties`
become editable, headers show a pencil or lock, and you can group rows. Turning the mode off
does not discard staged edits.
Scope the table to **All elements**, the current selection, or one loaded model. Edit cells, or
with grouping on use **Set all…** and **Set selected…**. Cells that the object does not carry
show **Missing parameter** and are skipped. To add a parameter that does not exist yet, open
**Columns**, type a name in **New attribute name…**, and add it. You can insert, overwrite, or
clear values, but you cannot delete a parameter.
When you have unsaved edits, the footer shows the count with **Discard** and **Submit change
requests**. Fill in the title and optional Issue fields, then submit. Speckle creates an Issue
that stores the parameter changes. You should see a success confirmation, and the staged edits
clear.
After you submit, apply the Issue in the connector the same way as today. See the apply step on
[Parameter Updater](/beta/parameter-updater).
## FAQ
In 2026.9 you edit from **Elements** in the model viewer, not from a Data Conditioning widget.
The widget path from before 2026.9 is documented on [Parameter
Updater](/beta/parameter-updater).
Open a model that is already in the new data format, then open **Elements**. **Update
parameters** is hidden when the panel is very narrow; widen the dock until the pencil control
appears. See [Speckle's data model is changing](/workspaces/data-model-migration) if the model
has not moved yet.
Yes. Submit still creates an Issue, and you still apply it from the connector Issues panel. Host
support, connector version, and apply-time limits are unchanged. See [Parameter
Updater](/beta/parameter-updater).
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.