# Instances

![Instance Editor](/files/-M6eVBhwVdYJ0ePfdLbH)

1. **Attribute Editor**\
   All attributes from the parent Dimension are displayed inside the editor pane, with default values set in the populated by default. 
2. **Subinstance Accordion**\
   Clicking on the accordion will display the attributes for the subinstance. Existing instances of the same Dimension type can be used to populate the values in the editor (read further for more details). 
3. **Editor Panel**\
   This panel allows you to change the properties of your Instance. 

### Subinstances

When the accordion is expanded, you can edit the properties of the subinstance. When changes are saved, the subinstance will be created as a distinct instance - for this reason, the "Instance Name" field is required.  

![](/files/-M6iIzZ6Gt0ajiAnhRCv)

You may also choose to use an existing instance of the same Dimension type, using the select box in the accordion.

![](/files/-M6iLBLb3ZasQrEHW5FA)

Subinstances that are already saved are read-only by default, and may be edited by selecting the "Edit" option from the menu on the right side of the accordion header.

There are two options for editing a subinstance.

**Edit Instance:** all changes will be saved against the selected instance, and will be reflected anywhere else that uses this same instance (including any other instances that use this as a subinstance). 

**Make a copy:** the values from the current instance are copied into a new instance, which will be created on save. A unique name must be given to this new instance.

![A copy cannot be made until a unique name has been entered](/files/-M7gu9jc18w8MeIB_AZ3)


---

# Agent Instructions: 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:

```
GET https://manual.senseforce.io/manual/sf-platform/machine-master-data/instances.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.