Embedded mode

The objective

The deeper integration: Launch Pad screens render inside your product's UI, in an iframe, with Launch Pad's own navigation hidden and a partner theme applied - to your user it reads as one application. The recipe is the same two steps as companion mode; only the handoff changes.

  1. The plumbing - identical to companion mode: your backend provisions Grower > Farm > Field > Boundary (GFFB) via the API.
  2. The handoff - instead of a new window, your page embeds <iframe src=".../path-planning/boundary/{id}?embedded=true&chrome=false">.

1The plumbing - behind the scenes, in your backend

Same three calls as companion mode - if you already ran them there, the wizard offers to reuse the field.

2The handoff - Launch Pad inside your page

Expect a login form inside the frame: browsers partition iframe storage, so a Launch Pad session from a normal tab does not carry over - sign in once inside the frame. Partner mode removes this: the frame URL carries a single-use launch code exchanged for a session on arrival, which works even in partitioned iframes. The frame switches to Launch Pad's built-in partner theme automatically; individual partner color schemes are not available yet.

Run the plumbing above to load the embedded view.