Infigo Core for Iframes

Quick facts
Level: Beginner
Estimated time: 1 hour
Last updated: 31/3/2026

This pathway is a short “admin foundations” series for iFrame (embedded editor) customers: your own website/portal is the customer-facing shell, while Infigo Admin is where you manage the behind-the-scenes building blocks (platform/storefront scope, users, products, and what happens after a job is created). It deliberately avoids deep implementation/API setup, and instead builds the mental model your team needs so the dedicated iFrame documentation “clicks” afterwards. 

What you’ll learn

By the end, a learner should be able to confidently:

  • - Work in the correct scope (platform vs storefront) and avoid “right change, wrong place” errors.

  • - Navigate Admin efficiently (top header utilities + left menu structure/search).

  • - Create/manage the key accounts involved in iFrame workflows (admins + registered users), understand role-based access, and recognise key identifiers like Customer GUID (and why it matters).

  • - Find/manage products and reliably capture/store the Infigo Product ID for external-to-Infigo linkage.

  • - Understand what a Job ID is for, and the difference between output-only flows vs recording orders in Infigo—plus where to review outcomes in Admin (Sales Orders / Print Operations).

  • - If orders are created in Infigo: review and progress them using Sales Orders (order-record view) vs Shared Print Operations (job/production view).

Who this is for

iFrame customers whose end users personalise products inside an embedded editor, but whose internal team needs to run the operational/admin side in Infigo (customer setup, product linkage, and optionally order handling).

Prerequisites

  • Infigo Admin access (platform admin or storefront admin credentials).

  • A basic understanding of your own external storefront/portal flow (because Infigo is being used as the “engine” behind your customer experience).

  • For best results: someone in your team who owns the iFrame integration can translate “concepts” (Job ID, output-only vs Record Order) into your real implementation approach.

Recommended further learning

Extra resources to deepen your understanding.

Help us keep this pathway up to date

Spotted something outdated, unclear, or not working as expected? Send us a quick note — we’ll take a look and keep things current.

Tip: If it’s outdated, tell us what you see now vs. what the tutorial shows.

Page: Loading…
URL: Loading…

We’ll prefill an email with the page title + URL to make reporting quick. Your message stays in your email app until you hit send.