> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cloneable.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Use Cloneable with IQGeo
> Field IQGeo scenarios in Cloneable and send the results back to IQGeo
The Cloneable Chrome extension connects IQGeo to Cloneable. Your design team's scenario comes into Cloneable as a job, fielders capture it in the Cloneable app, and the changes go back into IQGeo.
```mermaid theme={null}
flowchart LR
A["IQGeo scenario"] -->|"From IQGeo"| B["Cloneable job"]
B --> C["Field capture
Cloneable iOS app"]
C -->|"To IQGeo"| A
```
Nothing changes in IQGeo until you send. Setting up and bringing a scenario in only read from IQGeo.
## Before you start
Free from the Chrome Web Store. Already have it for Katapult? It's the same extension.
You need three things in the same Chrome profile:
1. **The Cloneable extension** installed from the [Chrome Web Store](https://chromewebstore.google.com/detail/cloneable/lhcnlckpplkmdiofklhinjjbohcocjpc).
2. **IQGeo** open in a tab and signed in.
3. **Cloneable** at [app.cloneable.ai](https://app.cloneable.ai) signed in. To set up, your account must be able to manage configurations.
The extension uses your existing IQGeo and Cloneable sign-ins. It never asks for or stores your passwords, and everything it writes to IQGeo is recorded under your IQGeo user.
If your IQGeo isn't on an `iqgeo.cloud` address, open the extension's Home screen, go to **Private servers**, add your IQGeo address, and allow access when Chrome asks.
## Open the extension
Click the Cloneable icon in Chrome's toolbar. If it isn't there, pin it from the puzzle-piece menu. With your IQGeo tab active, the side panel shows IQGeo with three tabs: **Set up**, **From IQGeo** and **To IQGeo**.
A green dot at the top shows the panel is connected, with your IQGeo address and IQGeo user. The letter at the top right is the Cloneable account you're signed in with.
## Set up Cloneable for your IQGeo
You do this once per IQGeo. The extension reads IQGeo's forms, option lists and icons and creates a Cloneable configuration that every scenario uses. Nothing changes in IQGeo.
Click the **Set up** tab. The list at the bottom shows any IQGeo configurations your organization already has.
Click **Step 1 · Read the IQGeo model**. Next to **IQGeo model**, the panel shows how many feature types, option lists and icons it read.
If IQGeo's map hasn't finished loading, the panel reloads the IQGeo tab. Save any open IQGeo form first.
Keep the default feature types under **Include**. They cover everything fielders use.
* **Name** is what people pick when they bring a scenario in. The default is "IQGeo Fielding".
* Leave **Use IQGeo's icon artwork** ticked so the Cloneable map looks like IQGeo's.
* Leave **Conventions** on None unless Cloneable has given you a conventions file.
Click **Step 2 · Check what will be created**. The extension rehearses the whole setup without creating anything, then lists the templates, dropdowns and map icons it will make. Open **What's in each template** to see the fields.
Click **Step 3 · Create**. If anything goes wrong, everything made along the way is removed, so you never end up with half a configuration. Click **Open the configuration** to see it in Cloneable.
What the configuration carries over from IQGeo:
| In IQGeo | In Cloneable |
| - | - |
| Field forms for poles, anchors, aerial spans, underground paths, terminals and so on | Object templates for poles, guys and anchors, spans, lines and points |
| Option lists | Dropdowns with the same labels |
| Mandatory fields | Fields required to complete the object |
| Allowed ranges, such as pole height | The same ranges, flagged as fielders type |
| Map icons | The same icons on the Cloneable map |
## Bring a scenario into Cloneable
Click the **From IQGeo** tab. Bringing a scenario in never changes anything in IQGeo.
Click the scenario's outline or title on IQGeo's map. Its name appears under **Scenario** in the panel.
Under **Configuration**, choose the IQGeo configuration you created during setup.
**What to bring in** shows how many of each feature type are inside the scenario. Keep the defaults and keep **Bring photos along** ticked.
Under **Into**, leave **New job**. The job is named after the scenario. You can change the name, or choose **Existing job**.
Click **Bring N features into Cloneable** (N is the total of the ticked types). When it finishes you see how many features were created and how many photos were uploaded. If anything fails, it is listed with a button to retry just those.
Click **Open in Cloneable** to see the job on the Utility Map. Fielders now see it in the Cloneable app.
Bringing the same scenario in again updates that job. Nothing is duplicated. From version 2.2.1, spans that cross the scenario boundary also bring their pole on the far side, locked, so the span stays connected.
## Field the job
Fielders open the job in the Cloneable iOS app and work through each object. Every template shows the fields IQGeo requires, for example "13 of 15 required fields remaining" on a pole, and flags values outside IQGeo's allowed ranges as they type. Photos go in the photo fields on each object.
## Send changes back to IQGeo
Open the **To IQGeo** tab. It works in three steps: **Job**, **Review** and **Send**.
Search for the job and click **Load**. The extension checks the job against IQGeo before anything is written. A configuration check shows anything IQGeo requires that the job doesn't fill.
You see how many features will be updated or added, how many are held back and why, and how many already match IQGeo. Each held-back group says how to fix it in Cloneable, for example "No pole height: measure the pole height in Cloneable", with links to the objects.
Features deleted in Cloneable are only deleted in IQGeo if you tick **Delete these in IQGeo when I send**. Features that existed in IQGeo before Cloneable are never deleted, only unlinked.
Tick the **Write to** box, which names your IQGeo address and warns that changes are live. Then click **Send N changes to IQGeo**. The box unticks after each send.
To try one pole first, open **Check a pole before sending**, preview it and click **Send only this pole**.
When it's done, the panel says how many IQGeo features are linked to the job. Sending again only sends what changed in Cloneable since the last send. If everything matches, you see "Nothing to send".
Sending is limited to the scenario the job came from. New and moved features must be inside the scenario boundary, and updates must be to features in that scenario. If the extension can't confirm that, it sends nothing.
## Next
Messages you might see and what to do.
Message us from the chat in Cloneable.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.