Applies to: All customers.
In this guide
A. Roles and permissions at a glance
The table below is the intended model of who does what in practice. "Cloneable" means a Cloneable staff member handles it for you.
Task | Org Admin | Team Admin | Analyst / Fielder | Analyst (Read-only) | Basic User |
Sign in, view jobs and data | Yes | Yes | Yes | Yes | Own data |
Collect and edit data, import and export jobs | Yes | Yes | Yes | No | Own data |
Build and edit configurations | Yes | No | No | No | No |
Store the Katapult secret | Yes | No | No | No | No |
Invite, remove, and change the role of users | Yes | No (today) | No | No | No |
View the analytics dashboard | Yes | No | No | No | No |
Set up and wire triggers | Cloneable | n/a | n/a | n/a | n/a |
Manage Katapult-linked configuration fields | Cloneable | n/a | n/a | n/a | n/a |
Set up single sign-on and API keys | Cloneable | n/a | n/a | n/a | n/a |
Team-level member management is currently performed by an Org Admin in the web portal (Settings, then Organization, then Teams); the Team Admin role does not yet unlock those screens, and roles there are chosen at invite time (remove and re-invite to change one).
B. Glossary
Configuration. The reusable template that defines a job's fields, photos, dropdowns, map colors, units, and measurement workflows. One configuration powers many jobs. See Configuration.
Data-object template. The definition of one kind of map object (pole, span, span measurement, guy anchor, or a custom point, line, or polyline) inside a configuration. See Configuration.
Model versus job. Importing a Katapult model builds your configuration (done once). Importing a Katapult job loads a single project's data (done per project). See Steps 1-2: Select your job and set status.
Trigger. The automation that moves data between Cloneable and Katapult. Set up by Cloneable. See Triggers: the Katapult connection.
Secret. A sensitive value (like your Katapult API key) stored encrypted in the secrets vault. See Store your Katapult API key.
Round trip. Importing a Katapult job into Cloneable, collecting in the field, and exporting the data back to Katapult. See Start here.
HOA (height of attachments). The measured heights of everything attached to a pole, placed and classified on the scaled pole photo. See Steps 6-7: Pole form, height, and HOA.
Birthmark. The burned-in stamp or placard on a pole showing its height, class, and species. See Steps 6-7: Pole form, height, and HOA.
SCID. The sequential pole number, assigned automatically. See Steps 6-7: Pole form, height, and HOA.
Overlash. Attaching a new cable alongside an existing one on the same strand, rather than running a new attach. See Steps 6-7: Pole form, height, and HOA.
New attach. A new cable attached to the pole independent of any existing line, as opposed to an overlash. See Steps 6-7: Pole form, height, and HOA.
Make-ready. Work required on a pole to prepare it for a new attachment (relocating or replacing existing equipment to create clearance).
Guy anchor. A down-guy wire and its ground anchor, which stabilizes a pole against tension. See Steps 8-11: Guys, midspans, and adding objects.
Midspan. A wire-height measurement taken between two poles, usually at the lowest point of the span. See Steps 8-11: Guys, midspans, and adding objects.
C. Job-status table
Status | Color | Meaning |
Draft | Amber | Not yet started from a Cloneable standpoint |
In Progress | Blue | Someone is actively working on it |
Complete | Green | Work is finished |
Cancelled | Gray | Set aside; safe to redo or clean up |
Status is a communication tool for the team. It is purely a visibility flag; changing it does not trigger an export, notification, or lock in the app. The first state is stored internally as "pending" and shown as "Draft" in the jobs list; the job detail side panel and archived-jobs filter still show "Pending" and "Completed" (with Cancelled shown in red in the job detail side panel). The status is set in Steps 1-2: Select your job and set status and surfaced in Analytics and export operations.
D. Device and account notes (field-only)
RTK GPS (optional, kit-dependent). An external Bluetooth RTK receiver (such as the Emlid Reach RX) gives centimeter-level positioning for placing poles and anchors, with corrections through its companion app and an on-map status indicator. If you do not have the kit, the app uses the iPhone's GPS.
Managing device storage. The app uses several GB (job data, photos, and up to about 2 GB of cached map tiles, a storage cap rather than an auto-cache figure). Clear the map cache in Settings when you no longer need an area. Archive completed-and-exported jobs to free space (space is reclaimed after you log out and back in). Never use the iOS "Offload App" option, and only reinstall as a last resort, after confirming everything has synced. A device with 128 GB or more is recommended.
Jobs, folders, and archiving. Completed-and-exported jobs can be archived (admins can archive; the data is preserved and reversible). Jobs can be organized into folders/groups for routes or crews. The phone shows active jobs.
E. See also
Related articles. This appendix pulls together definitions, roles, and status meanings used throughout the help center. Use the links below to open the full article on any topic.
Device storage tips are in the Device and account notes (field-only) section above.
Help center is the live source of truth. If anything here conflicts with the help center, the help center wins. (Whether measured photos auto-star as the Katapult height photo is still being confirmed with Cloneable; treat starring as a verification step.)