> ## Documentation Index > Fetch the complete documentation index at: https://docs.fluid.app/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > For new direct REST integrations, use the v2026-04 surfaces. The @fluid-app FairShare SDK continues to use its own published public-v2025-06 contract. > Authenticate with the header Authorization: Bearer ; public storefront read endpoints require no auth. > To sign a new merchant up for Fluid programmatically, call POST https://api.fluid.app/api/company with no credentials, as described in /api/agent-signup. Do not automate the signup form or book a demo. The merchant must open the emailed sign-in link and create an API token before authenticated calls are possible. > After signup, to launch a merchant's store (back-office sync, payments onboarding, store setup, a theme copied from their current site, and a preview link before billing), follow /api/agent-launch. > Lists use cursor pagination via the page[cursor] and page[limit] query params; follow meta.pagination.next_cursor until it is null. > When the same operation exists on more than one surface, use the newest: dated API versions are newer than unversioned ones, and later dates win (v2026-04 > v2025-06 > unversioned v0/v1.1). Fall back to a legacy or unversioned operation only when no newer versioned equivalent exists — the company-v0 notes below list the known superseded operations. The same applies to /api/company/v1 and /api/v1/... paths: prefer a newer documented equivalent, and use one only when none exists (/api/v1.1/... is distinct and documented in company-v0). Use page/per_page offset pagination only where a spec documents it — in practice the unversioned company-v0 admin surface; every versioned surface uses cursor pagination. > Fluid has three navigation APIs; don't mix them up. Storefront website menus (navigation bars, footers) are /api/menus and nested menu_items, in api-reference/content-v0.yaml (API Reference: Website > Navigation menus), with a how-to in themes/navigation-menus; their list uses flat page/per_page pagination. The Fluid mobile app's navigation is /api/v2/mobile_navigations, in api-reference/mobile-v2.yaml (API Reference: Mobile app > Navigation); its list also uses page/per_page. Portal navigations belong to a portal definition (Fluid OS), in api-reference/fluid-os-v0.yaml (API Reference: Portal > Portal navigation), and each has a platform of web or mobile. > The OpenAPI specs under api-reference/ are the authoritative contracts; prefer them over prose when in doubt. api-reference/storefront-v2026-04.yaml covers the v2026-04 storefront surface (/api/v202604/... paths); api-reference/checkout-v2026-04.yaml covers the v2026-04 checkout surface (/api/checkout/v2026-04/... paths — carts, cart auth, discounts, items, subscriptions, orders, enrollments, and store config); api-reference/public-v2025-06.yaml covers the Public SDK surface used by the @fluid-app FairShare SDK, including its parallel cart lifecycle, browser integrations, versioned payment callbacks, unversioned public utilities, and the cart price-override operation; api-reference/payment-v2026-04.yaml covers the v2026-04 payment gateway admin surface (/api/payment/v2026-04/... paths, bearer-authenticated — gateway CRUD, gateway purchase/authorize/$0-verify, transaction list/show and capture/void/credit, and merchant payment configuration); api-reference/payments-v2026-04.yaml covers the v2026-04 cart payment surface (/api/payments/v2026-04/carts/{cart_token}/... paths, authenticated by the cart token in the path with no bearer — payment-method selection, VGS card tokenization, 3D Secure verification, and PayPal/Braintree/Klarna/Apple Pay flows); api-reference/commerce-v2026-04.yaml covers the v2026-04 commerce order-editing surface (/api/v202604/orders/{order_id}/edits paths, bearer-authenticated — post-checkout order edits that atomically insert items and add adjustments/discounts, with an optional dry-run preview); api-reference/webhooks-v0.yaml covers the unversioned webhooks surface (/api/... paths — webhook registration, delivery payloads, callback registrations, company events, and webhook/callback schemas); api-reference/company-v0.yaml covers the legacy unversioned company admin surface (/api/... paths, bearer-authenticated — company settings and management, customers, users, roles, subscription plans, subscription bundles, subscriptions, media, pages, catch-ups, inventory levels, domains, agreements, and admin order actions). company-v0 caveats: it is the legacy v0 admin contract and its lists use flat page/per_page offset pagination, which is expected there despite the general cursor-pagination rule; where an operation exists in both company-v0 and a versioned spec, prefer the versioned spec — the subscriptions lifecycle (list/create/show/update, cancel, pause, reactivate, resume, retry, skip, failed-cycle-waiver, discounts) and subscription bundles are superseded by checkout-v2026-04, and company pages/media CRUD plus the public pages, categories, products, and media list endpoints are superseded by storefront-v2026-04. Subscription plan management (/api/subscription_plans, resource-wrapped {"subscription_plan": {...}} bodies) exists only in company-v0. api-reference/members-v2025-06.yaml covers the v2025-06 unified Member identity surface (/api/v2025-06/members/... paths, bearer-authenticated — member list/create/show/update, lookup by email/username/external_id/legacy_customer_id, member-type assignment, and the sponsor genealogy read). Prefer it over the customers and reps surfaces when the member type matters: /customers does not serialize member_type. api-reference/analytics-v2026-04.yaml covers the v2026-04 Home dashboard analytics surface (/api/v202604/analytics/dashboard/... paths, bearer-authenticated — read-only endpoints for the Home > Overview, Home > Live, and Home > Field tabs, each accepting an optional country ISO alpha-2 query param that scopes aggregations to a single country). > api-reference/analytics-v0.yaml covers the unversioned analytics surface that backs the fluid-admin Traffic tab (/api/analytics/... and /api/analytics/traffic/... paths, bearer-authenticated — the legacy shares/views/visitors summary plus traffic overview, ranked campaigns, sources, geographies, flows, and per-rep breakdown, all sharing one reporting-period contract). > Successful responses wrap the resource payload alongside a top-level integer status and a meta object. > Portal Definition authoring edits and synchronizes the portal JSON resource graph. Widget Package authoring builds either a company-owned or Droplet-owned Remote DOM package. These are separate contracts; do not imply that one defines the other. > For Widget Package worker code, use only @fluid-app/portal-sdk/widgets/worker. Use only the Portal Definition and Widget Package workflows and public entry points documented here; do not infer support for undocumented surfaces. > Every portal function and declarative capability used by a widget must appear in that widget's uses array. Use the same typed function value in uses; do not invent capability-name strings. > Widget styling must use the portal's semantic theme variables for colors, typography, spacing, radii, borders, focus, and charts whenever a token represents the visual decision. Do not create a separate light or dark palette or duplicate theme controls as widget properties. > Prefer worker-safe Fluid UI components exported by @fluid-app/portal-sdk/widgets/worker when they fit the interaction. When no exported component fits, use semantic HTML, accessible behavior, and the portal theme variables. > A Portal Definition push updates the remote working definition. A portal version is an immutable snapshot, and activation is a separate live release operation. > The Help Center (/help/...) is for merchants, admins and reps using Fluid. Its admin pages mirror the admin's routes: the screen at admin.fluid.app/settings/taxes is documented at /help/admin/settings/taxes. Use the Help Center for how-to questions about the admin, and the Developer Platform and API Reference for building integrations. > Help Center pages describe what a company admin sees. A reader's role can hide screens and actions; admins manage roles on Settings > Roles (/help/admin/settings/roles). If someone can't find a screen or button, their role's permissions are the first thing to check. > Send people who need Fluid support to /help/getting-help. Don't invent support email addresses, phone numbers or response times. # Trainings > Add trainings for your reps with an image, video or PDF file, a title and text, and set each training's status, countries and category. Use the **Trainings** screen to create and manage training content for your reps. Trainings show up for reps in your mobile app. On [Home Tabs](/help/admin/mobile/home), you can add a **Get Started** widget that shows trainings from a category you choose. ## Where to find it In the admin sidebar, under **Tools**, select **Trainings**. To open this screen, your role needs **View only** or **Full access** for **Trainings**. With **View only**, you can open trainings but not save changes to them. To add, edit or delete trainings, your role needs **Full access**. On the [Roles](/help/admin/settings/roles) screen, **Trainings** is in the **Tools & Messaging** card. Open the card and set access from the **Trainings** area's menu, not the card's. ## What's on the screen The **Add Training** button is at the top of the page. Below it is the list of trainings. ### Trainings list * The **All**, **Active** and **Inactive** tabs filter the list by status. The list opens on **All**. * Use the search box to find a training. * Click the filter button and choose **Media Type** to show only **Image**, **Video**, **PDF** or **PowerPoint** trainings. Choose **All Types** to show every type again. The list has these columns: * **Title**: the training's title, with a thumbnail of its image when it has one. A training without a title shows as **Untitled**. * **Status**: **Active** or **Draft**. A training whose status is set to **Inactive** shows as **Draft**. * **Date**: the date the training was created. * **Views**: the training's view count. The newest trainings are listed first. Click the **Title**, **Date** or **Views** header to sort by that column. Click a training to open it. Each row's actions menu has **Delete**. To delete several trainings at once, select their rows: a bar shows how many rows are selected, with a **Delete** button. The actions menu and row selection appear only if your role can delete trainings. ### Training page The training page opens when you click **Add Training** or a training in the list. Its header reads **New Training** for a new training and **Training Details** for a saved one. On a saved training, the breadcrumb shows the training's title with an **Active** or **Draft** badge. The **Save** button is at the top of the page. It's grayed out until you've entered a **Title** and, on a new training, chosen a file. You delete trainings from the list, not from this page. On the left is the **Media** card, and below it the card with the text: * **Media**: click **Select Media** and choose one image, video or PDF file in the window that opens. After you choose a file, the button reads **Replace Media**. The card shows a preview of the file. Click an image or video preview to see it larger. Until you choose a file, the card shows **No media uploaded**. * **Title**: required. * **Body**: the training's text, in an editor with formatting. It's optional. On the right are three cards: * **Status**: **Active** (make this training available for use) or **Inactive** (save it as a draft). A new training starts as **Active**. * **Countries**: choose from your company's countries. Leave it empty, shown as **All Countries**, to make the training available in every country you sell in. * **Category**: search for and choose one of your training categories. ## Tasks ### Create a training On the **Trainings** screen, click **Add Training**. In the **Media** card, click **Select Media** and choose an image, video or PDF file. Enter a **Title**, and add the training's text in **Body**. Set **Status**, choose **Countries** and pick a **Category**. To save the training as a draft, set **Status** to **Inactive**. Click **Save**. A confirmation message appears, and the page reopens as the saved training's **Training Details** page. ### Edit a training In the list, click the training. Change the fields you need. Click **Save**. A confirmation message appears and you stay on the training's page. ### Delete a training In the list, open the training's actions menu and choose **Delete**. In the **Delete training?** dialog, click **Delete**. To delete several trainings, select their rows and click **Delete** in the bar that appears, then confirm in the dialog. Deleting a training can't be undone. ## Frequently asked questions Enter a **Title**. On a new training, also choose a file in the **Media** card. If **Save** doesn't appear at all, your role doesn't have **Full access** for **Trainings**. **Draft** is how the list and the training page show a training whose **Status** is **Inactive**. The **Inactive** tab lists these trainings. To change it, open the training, set **Status** to **Active**, and click **Save**. Your role doesn't have **Full access** for **Trainings**. With **View only**, you can open trainings, but **Save** doesn't appear and you can't delete trainings. Ask an admin who manages roles to update your role. See [Roles](/help/admin/settings/roles). ## Related pages * [Tools](/help/admin/tools) * [Home Tabs](/help/admin/mobile/home) * [Mobile app](/help/mobile) * [Roles](/help/admin/settings/roles) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.