Skip to main content

Week of September 18 – September 25, 2026

iOS app 2.8.0 released — map-centric search and Assigned to Me layer

Version 2.8.0 shipped to the App Store this week. The headline change is map-centric search: search now happens directly on the map with a “search this area” flow, mirroring the search redesign already live on web. For sales reps, a new Assigned to Me layer surfaces the operations and contacts assigned to that rep or account manager (loads up to 2,000 records at a time). Contacts also gained in-app editing of the relationship manager field, and this release includes fixes for notes rendering, CarPlay pan mode, farm creation, and contact phone-number parsing. Requires iOS app version 2.8.0 or later. The Assigned to Me layer is currently enabled only for CamoAg’s own account while it’s tested further.

iOS app 2.8.1 — search polish release

A follow-up polish release shipped September 23, refining the 2.8.0 map search experience. Choosing a search suggestion now drops the results sheet to half height and gets the keyboard out of the way (matching the behavior of Google/Apple Maps), the map centers the result in view, and addresses now show a Directions button. Default locations update immediately when changed in Settings, My Saves remembers your page and scroll position, and several farm and contact permission bugs are fixed. CarPlay cold starts now show the Assigned to Me layer as well. Requires iOS app version 2.8.1 or later.

Assigned to Me operations layer — coming to web

The same Assigned to Me concept from iOS is being built for the web map, surfacing a rep’s or account manager’s assigned operations and contacts directly on the map. It’s currently behind a feature flag while it’s tested internally, so most users won’t see it yet.

Crop allocation editing on Operation Profile

Building on last month’s read-only crop breakdown, the Wallet Share card under Operation Profile → Revenue now lets you edit the per-crop revenue allocation directly, with save and cancel controls and validation that flags when allocations add up to more than 100%. Requires CamoAg Pro and a feature flag (private beta). Reach out to your CamoAg account manager to request access.

Small search result quality improvement

A small backend improvement now applies across all four search services: “search this area” results get an extra pass that can surface a good match that would previously have been filtered out by a stricter confidence check. Available to all users using search.

Admin: developer permission retired

The deprecated developer organization permission has been removed from Admin. Anything that previously depended on it should use the “Manage Embed SDK credentials” permission instead. Requires Admin access.

Faster Contacts report data

The Contacts report now refreshes its cached data every hour instead of every 6 hours, so changes across your contact base show up sooner. Requires Contacts reporting access.

Fixes and polish

  • User Management profile pictures — fixed a bug that kept your profile picture from appearing on your user card in User Management.
  • Recent search results — fixed a display bug affecting recent search examples in map search.
  • Duplicate notifications — fixed an issue that could show the same confirmation toast twice.
  • Parcel search infrastructure — an internal upgrade to how parcel address search is processed; you may notice a small improvement in address-search matching, but no other visible change is expected.

Week of September 12 – September 18, 2026

Redesigned operation merge is now on for every account

The updated merge operation flow — guided search, a side-by-side review of both operations, then a confirmation step is now enabled for all accounts. Requires CamoAg Core. The operation must be saved to your account (Save to edit).

Livestock

Livestock is now visible on every subscription. Livestock data on an individual operation can be viewed on Core, Scout, and Enterprise. Livestock reporting still requires an additional subscription. Users with the Edit Operations permission can edit livestock data on an individual operation.

Operation Revenue — crop-level breakdown

The Wallet Share card under Operation Profile → Revenue now includes a per-crop breakdown and an assumptions table, so you can see how an operation’s estimated revenue is distributed across crops and which per-acre assumptions produced it. This view is read-only for now; editing and saving your own assumptions is in progress. See Revenue and Total Addressable Market (TAM) for how the numbers are calculated. Requires CamoAg Enterprise and a feature flag (private beta). Reach out to your CamoAg account manager to request access.

Default API version moved from v5 to v7

The platform’s default API version was raised from v5 to v7 across the application. If your organization calls the CamoAg API directly, note that v3 and v4 have now been removed entirely.

Refreshed documentation site

docs.camo.ag has been rebuilt. Articles have moved off the old help-center URL structure (numeric article IDs) onto clean topic paths such as comp-tool, reports, contacts, and map, and navigation is now organized into Docs, Admin, iOS, Release Notes, Guides, Training, and Developers tabs. Old help-center links redirect to their new homes, so existing bookmarks and links shared with customers keep working. New material landed alongside the move, including a full iOS section (getting started, CarPlay, farms, parcels, contacts, operations, notes), operations depth on deep research, revenue/TAM and merging operations, contact enrichment and address import, SSO and API client documentation, a consolidated reports and data sources reference, and a tag-filterable Guides index.

Fixes and polish

  • Merging polygons — fixed a bug in the merge flow that could produce an incorrect combined boundary when merging parcel or field polygons.
  • Boundary edit tools — the explanations shown when a boundary editing tool is unavailable are clearer about why it’s disabled and what to do instead.
  • Legacy Salesforce links — links into CamoAg from older Salesforce records had stopped resolving. Those routes have been restored.

Week of September 6 – September 12, 2026

Change an operation’s contact type

You can now switch an operation’s contact type between Customer and Prospect directly from the operation, instead of editing each contact underneath it one at a time. Two things to know before you use it:
  • It applies to every contact on the operation. If an operation currently holds a mix of Customer and Prospect contacts, switching the operation’s type flips all of them to your choice. Getting the mix back means editing those contacts individually.
  • Third-party managed contacts are excluded. If an operation contains contacts managed through an outside system such as Salesforce, the control is disabled and shows a lock icon. Contact type for those records should continue to be managed in the source system.
Requires CamoAg Core, the operation must be saved to your account (Save to edit).

Redesigned Map Tools menu

The Map Tools menu has a new, sleeker design that groups the tools into a single card and uses a unified panel motion. The practical win is vertical space — the old menu consumed a large share of the map on shorter screens. Available to all users who can add farms.

Operation Revenue — Purchases and Wallet Share

A new Operation Revenue section on the operation profile surfaces purchase history and wallet share for an operation. See Revenue and Total Addressable Market (TAM) for how the numbers are calculated and what data your organization needs to provide. Requires CamoAg Enterprise and is currently in private beta. You also need to be logged in as part of an organization that has revenue data loaded.

Help and support moved from Zendesk to HubSpot

Our help desk and in-app support widget now run on HubSpot. Zendesk has been retired. The support entry point has moved — see the in-app widget for its new home. As part of the swap we added a pre-populated parcel assessor link report form. When a county changes the URL behind a parcel’s assessor link, you can flag it in a couple of clicks rather than writing up a support ticket. Available to all paid subscribers.

Key People and confidence scoring available in Omni

The Beta Key People concept, along with its Low / Medium / High confidence rating, is now available in select reporting. Sharing a platform link in Slack, iMessage, or on social now renders a proper large preview card across all brands, including whitelabels. Previously some brands previewed with no image at all, and the shared artwork was cropped awkwardly on most platforms because of its aspect ratio. One card is now used for every brand.

Fixes and polish

  • Map Layers menu on company layers — fixed an issue where the Map Layers menu rendered empty when adding a new company layer or opening a layer’s details to edit. (CamoAg Enterprise)
  • Highlight on the Map — Buildings — Parcel Buildings requires a CamoAg Enterprise subscription to view, so the Highlight on Map option is now correctly hidden for non-Enterprise users rather than appearing and doing nothing.
  • Date of birth validation — fixed validation on the date of birth field in the create and edit contact forms, including the split day/month/year input, so invalid dates are caught at entry instead of on save.
  • Operation preview panel styling — a pass over the map operation preview: tightened header and section padding, a full-height divider next to acres, consistent accordion header icons, and reduced side padding on the map menu header.

iOS Mobile app — TestFlight builds (2.8.0)

These are internal TestFlight builds working toward the 2.8.0 App Store release.
  • Wetlands map layer on iOS (build 154) — the web Wetlands layer is now ported to iOS and viewable on the phone. Not yet available in CarPlay.
  • Edit relationship manager from mobile (build 156) — for contacts you’re able to edit, the relationship manager can now be set in the create and edit contact flow.
  • Phone number paste fix (build 155) — pasting a phone number copied straight out of the iOS Contacts app used a format that triggered an API error when creating a contact. That format is now handled.
Last modified on September 25, 2026