> ## 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. > 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. /api/company/v1 and /api/v1/... paths are documented in no spec here and must never be used (/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. > Navigation menu management is documented in themes/navigation-menus. These unversioned admin endpoints (/api/menus and nested menu_items) are verified against the implementation but are not yet in the synced OpenAPI specs. Use that reference for menu payloads and its flat page/per_page pagination; missing spec coverage does not make these endpoints unavailable. > 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. # Communications > Choose the service that sends your company's emails and set each email type to Active or Inactive. This screen controls how your company's emails go out. The **Email Delivery Provider** card sets who delivers them. The table below it lists each email type with its status. ## Where to find it In the admin, click the **Settings** gear in the top bar. In the Settings sidebar, under **Company**, select **Communications**. Your role needs these permissions, as named on the [Roles](/help/admin/settings/roles) screen: * At least **View only** for **Company Settings**, in the **Settings** card, to open this screen. * **Full access** for **Company Settings** to set emails to **Active** or **Inactive**. Without it, **Save** doesn't appear, and the switches, tabs, search box, page buttons and **View Droplets** are disabled, so you see only the first page of emails. * **Full access** for **Company Settings**, plus the **Integrations** switch **Configure integration settings** in the **Settings** card, to save a provider change. * The **Droplets** switch **Browse the droplet marketplace and installed droplets**, in the **Tools & Messaging** card, to open the **Droplets** page. ## What's on the screen ### Email Delivery Provider Pick one option: * **Fluid Email (Default)**: sends your emails through Fluid's email service. * **Use a Droplet**: sends your emails through your own provider using a droplet integration. While this option is selected, a **View Droplets** button appears. It opens the **Droplets** page. With **Use a Droplet** selected, Fluid hands your emails to your provider only when your company has an active `deliver_email` [callback](/help/admin/settings/callbacks), such as one that an email droplet sets up. Without one, Fluid keeps sending your emails itself. With **Use a Droplet** selected and that callback active, if handing an email to your provider fails, the email isn't sent. Fluid doesn't send it itself instead. ### Email table Each row is one email type. The table has three columns: * **Type**: the email's name, for example **Order Confirmation** or **Subscription Reminder**. * **Description**: a short note on what the email is for. * **Status**: an **Active** or **Inactive** badge, next to a switch. Above the table, use the **All**, **Active** and **Inactive** tabs to filter the list. Use the search box to find an email by its type or description. Most types start with a word that names their group: * **Order**: includes confirmations, notifications for your admins, refund receipts, fulfillment notices and cancellation notices. * **Subscription**: renewal reminders, invoices, confirmations, and notices when a subscription skips its next billing, is paused, is cancelled or resumes. It also includes emails about a failed payment, a past-due subscription and a request to update a payment method. * **Messaging**: new message notices, unread conversation reminders, and notices about premium messaging, phone numbers and TrustHub profiles. * **Notification**: cart activity and abandonment, announcements, overdue tasks, comment replies, mentions on theme preview comments, page views, video activity and upcoming events. * **Export**: notices that a product export or a data export is ready. * **Enrollment**: enrollment completion reminders, and the portal invitation sent when a member completes enrollment. The **Notification Cart Activity** switch also controls other notification emails, such as a rep's alerts about new orders and new leads, and mentions in messages. Setting it to **Inactive** stops those emails too. Mentions on theme preview comments have their own row, **Notification Preview Comment Mention**. Rows outside those groups include: * **Auth Signup Confirmation**: email address confirmation for new sign-ups. * **Comment Reply Notification**: emails a contact when someone replies to a comment the contact left. **Notification Comment Reply** is a separate row, for reply notices that go to people on your team. * **Promotion Promo Code**: delivery of promotional codes. ## Set an email to Active or Inactive Use the tabs or the search box above the table. In the **Status** column, turn the switch on to make the email **Active**, or off to make it **Inactive**. The change saves right away, and a confirmation message appears. You don't need to click **Save**. ## Change the email delivery provider Under **Email Delivery Provider**, select **Fluid Email (Default)** or **Use a Droplet**. **Save** becomes available once you pick a different option. Click **Save** at the top of the page. A confirmation message appears when Fluid saves the change. **View Droplets** takes you away from this screen. If you switched to **Use a Droplet**, click **Save** first so your choice isn't lost. ## FAQ No. This screen doesn't change what an email says or when it's sent. No. The banner at the top of this screen mentions sender details, but the screen has no sender or reply-to setting. No. The banner at the top of this screen mentions abandoned checkout emails, but the screen doesn't set up follow-up emails to customers who abandon a checkout. The **Notification Cart Activity** row covers the cart activity and abandonment notifications that go to your reps. No. Passwordless sign-in links, multi-factor sign-in emails and user invitations aren't listed on this screen, so you can't turn them off here. The portal invitation sent after a member completes enrollment is a different email, listed under **Enrollment**. ## Related pages * [Settings](/help/admin/settings) * [Roles](/help/admin/settings/roles) * [Callbacks](/help/admin/settings/callbacks) * [Droplets](/concepts/droplets)