Day-two work is different from first-time setup. You already have a configuration, and you need to open it, refresh what came from Katapult, or change selections without building a second copy by accident.
You need administrator access. Without it the page tells you that you do not have permission to create or edit configurations.
On the configurations list
Before you open a configuration, the list also offers:
Moving a configuration to a different organization uses the same two controls. Export it to a file while working in the organization that has it, then switch to the organization you want it in and use New Configuration > From a Cloneable file to bring it in there. There is no direct organization-to-organization transfer; the file is the handoff.
New Configuration, with Blank, Katapult model, KML, or Cloneable file.
Actions on the selected configuration: Export to file and Edit Katapult selections.
Enable Utility Pole Inspection, and Surface Measure (beta) when your org has those options.
Use Edit Katapult selections when you need to refresh the live configuration. Use New Configuration only when you mean to build a second one.
Open the configuration you already have
Go to Settings, then Configurations.
Open the configuration you want to change.
Use the stages on that configuration for units, templates, field options, workflows, and export. That path is the same stage-by-stage editor you used after the first import.
For the full stage list, see Set up your configuration, stage by stage.
Update from a fresh Katapult model
When your Katapult model has changed and you need those changes in Cloneable, reopen the import flow against the existing configuration. Cloneable runs that path in update mode (the address carries an update-config reference), so it revises what you already built instead of creating a second configuration with a second set of templates.
From the configuration's actions, choose the option that edits your Katapult selections (wording may read like Edit Katapult selections…). That reopens the guided import steps. At the end, the finish button reads Update config rather than Complete Import.
If the page says the configuration has no stored Katapult model yet, upload or store the model first with the update-model path the screen offers, then come back. Prefer storing your Katapult credential before you rely on import and export triggers. See Store the credentials your integrations need.
What stays locked when you update
Updating is not a free rewrite of every field.
The configuration name is often locked. Existing templates already carry that name as a suffix, so the update path shows the name but will not let you change it. On screen you may see that the name cannot be changed because existing templates are linked to it.
Steps still confirm and lock in order. Each step asks you to confirm before the next unlocks. You cannot skip ahead.
Mapping can hard-lock after you confirm it. Treat selectors you already confirmed as fixed for the rest of that run. Check before you confirm, not after.
Measurement unit and ground-line options that appear grayed out on step 1 of the import sequence may still be changeable later in the configuration's own settings stages. The name is the one to treat as permanent on this route.
Prefer update over a second import
Reopening the existing configuration keeps what you already built. Starting a brand-new import creates another configuration and another set of templates to tell apart when you create jobs. Use update when you are fixing or extending the configuration you already run.
For the step-by-step of what comes across from the model, see Choose what comes across from your Katapult model.
Related