What a configuration is made of

A configuration is built from data-object templates, one per kind of thing your crews place on the map:

Pole (the pole and its attributes, photos, and height measurement)
Span (the run between two poles)
Span measurement (a midspan measurement)
Guy anchor (a down-guy's ground anchor)
Custom points, lines, and polylines for anything else your work needs (for example service drops, reference markers, conduit runs, or right-of-way edges)

Each template carries its own fields, photos, and status colors. The configuration ties the templates together and holds the settings that apply to the whole job.

How a configuration gets built: importing a Katapult model

For Katapult customers, a configuration is built by importing your Katapult model once (see Getting Started as a Setup Admin / Implementer for the model-versus-job distinction). You import the model once, often together with Cloneable during onboarding; jobs are then imported many times after that.

Model import begins on the Katapult side, using the Katapult to Cloneable Exporter Chrome extension (link): in Katapult you choose to export the full model, the extension reads the Katapult Pro model and produces the JSON Cloneable imports, and this opens the Cloneable import wizard. This is usually done together with Cloneable during onboarding.

The model import is then a guided, step-by-step wizard:

Name your configuration.
Select model elements (which node and connection types to bring over).
Select attributes. For each type, you choose which attributes to bring across. Everything starts unselected, so you pick exactly what you want (Select All and Deselect All buttons and a search box help you work through the list quickly).
Map Katapult nodes (line up your Katapult node types with Cloneable's templates).
Configure Visualization Icons (the status colors, see below).
Configure triggers (this is where the import and export triggers get connected to the configuration; typically handled with Cloneable).
Final Review & Import.

Important: Step 3 is where the round-trip attribute rule kicks in. Only the attributes you select here become fields your crews can fill in, and only those fields can be written back to Katapult later. Leave an attribute out and it will not exist to round-trip (see the round-trip rule in Getting Started as a Setup Admin / Implementer).

Building a configuration without Katapult

If your organization does not use Katapult, a configuration is still required before any job (blank or KML) can be created, but it is built differently. An org admin can set one up without Cloneable: in the Configuration Manager, choose Create New, name the configuration, and click Create Configuration to generate a standard template set (Pole, Span, Span measurement, and Guy anchor templates, the pole and guy-wire measurement workflows, and the relationships between them) in one step. (A separate Configure from KML wizard can build a configuration from an uploaded KML/KMZ/GeoJSON file, but in the current portal it has no menu or button entry point and is reached only by its direct URL, so treat it as not yet surfaced.) Cloneable can also build your data-object templates directly and assemble them into a configuration in the Configuration Manager. On a configuration that is not tied to a Katapult model, you can also choose exactly which template fills each object-type slot (pole, span, and so on); Katapult-linked configurations pin those slots instead, to protect the mapping. Talk to Cloneable about your specific setup, especially if you need on-device height capture, since how a configuration was built can affect whether the measurement workflow is available.

What the fields, photos, and colors do

Fields and photos

Each template holds the fields a fielder fills in (text, yes/no, numbers, dates, pick-from-a-list, and photos). The set, order, and dropdown choices are entirely up to your configuration, which is why two organizations' forms can look completely different.

Required fields, two ways

A field can be required just to create the object at all, or required only to mark the object complete. This lets a fielder start a pole without every detail filled in, while still blocking "Complete" until the required fields are there.

Dropdowns are shared lists

A pick-from-a-list field pulls its choices from a shared list, so the same list of options can back more than one field, even across different templates. If your crews keep needing a choice that is not there, that is a configuration change: add the option to the list, rather than letting them type a wrong value in the field. Because the list is shared, adding it there makes it available everywhere that list is used.

Photos: single or multiple

A photo field can capture one image or a whole set.

Status colors

The color of a map dot reflects an object's status (for example, imported versus collected versus reviewed). This is sometimes called conditional map styling or icon rules. Status colors are set up per template, so poles, spans, and guy anchors each have their own independent set of color rules, built from three pieces:

A locked base rule. Every template starts with one that cannot be deleted or reordered.
Your custom rules. Each one pairs a condition (for example, "status is Collected," or a yes/no field is checked) with a color. Rules are checked in order and the first match wins, so put your most specific states first and leave a catch-all default last.
An automatic "Has Measurements" rule. Poles and span measurements get this one for free, on top of whatever you add; it lights up once height data exists.

Point objects like poles get a fill color; line objects like spans use only a line color, since there is no shape to fill.

A rule needs to match the field's actual stored value, not just how it looks in Katapult. A Katapult dropdown with Yes/No choices imports as the text "Yes" and "No," not the boolean true/false, even when it displays like a checkbox in Katapult. If a rule you wrote is not matching, check whether the field is really a Yes/No text value rather than true/false.

Units

You set whether measurements display in metric, feet and inches, or decimal feet. This setting controls display only. The underlying measurements are stored in metric, so values pulled straight from the raw data can read as metric even when the portal shows feet.

Measurement workflow

Poles, span measurements, and guy wires each use a measurement workflow. These are set up as part of the configuration; you do not need to manage their internals. Poles and span measurements capture height, while the guy workflow captures guy length and angle. Guy anchors themselves do not capture height, and carry simple fields such as the anchor's angle and lead length.

Editing a configuration later

Ongoing tweaks are made in the Configuration Manager in Settings. From there you can adjust the units, turn field measurement capture on or off, set the measurement workflows, and manage export settings. Status colors are edited in the configuration's icon setup. Fields can be added or removed by re-importing the model (Edit Selections); field or dropdown changes beyond that are handled with Cloneable. On a configuration that is not connected to Katapult you can also choose which template fills each slot; on a Katapult-connected configuration those slots are pinned to preserve the Katapult mapping, so that choice is not offered.

Two things worth knowing:

Re-importing a model updates the same configuration in place. If you need to add an attribute you left out, re-import the model into the existing configuration. You do this from the Configuration Manager's Edit Selections action (or, from a freshly captured model, Update Existing Configuration), which re-opens the wizard on the existing configuration so you can check the previously omitted attribute; it requires the configuration to have a stored model from its original import. It updates that configuration; it does not create a new one and does not duplicate your work. When you update an existing configuration by re-importing a fresh Katapult model, a change-review screen shows what will change before you apply it (the Edit Selections path, which rebuilds from the model you already imported, does not show that screen). This is the fix for the round-trip attribute rule.
Give each configuration a unique name. Reusing an existing name, including one you just deleted, has caused save and import errors. If creating or re-importing a configuration fails unexpectedly, try a different name before contacting support.
Cloneable holds the Katapult-linked fields. On a configuration that is connected to Katapult, the Katapult fields are locked so they cannot be renamed, retyped, or deleted. This protects the round trip. You can still add and arrange your own fields; if you need a Katapult-linked field changed, ask Cloneable.