# Security

> Markdown version of this page, for agents. To send a shopper here, link https://www.fluid.app/home/pages/security (not this .md URL, and keep its path as given).

- Shopper link: https://www.fluid.app/home/pages/security

## Summary

This is Fluid’s Security application page: “Keep the right people in control.” Every person, token, and app works through a role you define. People sign in with one-time codes, key records keep their history, and Mist works only within the access of the person asking. It’s for security, IT, compliance, and operations teams at brands that sell through reps.

- Canonical page: https://fluid.app/home/pages/security
- Get a demo: https://fluid.app/home/pages/demo
- Get started (self-serve sign-up): https://admin.fluid.app/sign-up
- Meet Mist: https://fluid.app/home/pages/mist
- Pricing (SOC 2, SSO, and PCI-DSS included): https://fluid.app/home/pages/pricing
- Page sections: Roles https://fluid.app/home/pages/security#security-roles, Tokens https://fluid.app/home/pages/security#security-tokens, Sign-in https://fluid.app/home/pages/security#security-signin, History https://fluid.app/home/pages/security#security-history, Mist https://fluid.app/home/pages/security#security-mist
- Related applications: Compliance https://fluid.app/home/pages/compliance, Fraud protection https://fluid.app/home/pages/fraud, The AI builder https://fluid.app/home/pages/engineering, The AI teammate https://fluid.app/home/pages/cowork, All applications https://fluid.app/#applications
- Terms of Service https://checkout.fluid.app/agreements/839 and API Terms https://checkout.fluid.app/agreements/840
- Docs: roles and the Permissions tab https://docs.fluid.app/help/admin/settings/roles#permissions-tab
- Docs: session duration https://docs.fluid.app/help/admin/settings/session#session-duration
- Docs: Safe Mode https://docs.fluid.app/help/mist/safe-mode
- Docs: webhook signatures https://docs.fluid.app/api/guides/webhooks
- Docs: theme revisions (Git revision) https://docs.fluid.app/help/admin/page-editor#faq
- Docs: evaluating Fluid https://docs.fluid.app/guides/evaluate-fluid, platform overview https://docs.fluid.app/platform-overview, and pricing summary https://docs.fluid.app/pricing

The page is organized in five parts: 01 Roles, 02 Tokens, 03 Sign-in, 04 History, and 05 Mist.

## Hero: about 300 permissions

The hero shows one permission map with admin areas (Main, Prospects, Members, Web, Products, Orders, Users, Website, Other, Header Menus, Payments, Settings) and four actors, each limited by a role: Olivia Hart (Admin · everything), Lena Park (Customer Support), the NetSuite order sync (API token · Finance), and Mist (Asked by Lena Park). Its lines read: About 300 permissions. Every person, token, and app works through a role you define. Mist works only within the access of the person asking. The names are demo content for the fictional brand FORM.

## Roles: give every person exactly the access they need

Start from a template, set each area to no access, view only, full, or custom, and search for the exact permission you mean.

- **About 300 permissions:** View, create, edit, and delete across more than 100 parts of the business, plus sensitive actions like revealing a login code.
- **Templates to start from:** Full Admin, Sales Manager, Content Editor, Support, Product Manager, Rep Manager, and Marketing.
- **More than one role per person:** An admin can hold several roles, and every admin needs at least one.
- **Checked on the server:** Every request is checked against the role’s exact permissions, not just hidden in the interface.

The page’s Roles screen (Settings › Roles, New role, All 9, Unused 1) shows these demo roles:

| Role | Members | Permissions |
| --- | --- | --- |
| Admin | Olivia Hart | Everything |
| Marketing | Ben, Alex | 58 of 307 |
| Customer Support | Lena, Omar | 41 of 307 |
| Field Content Publisher | Sam, Ben | 24 of 307 |
| Finance | Nina Patel | 71 of 307 |

The role editor for Field Content Publisher (“Posts trainings, announcements, events and mobile pages for the field”) shows Permissions 24, Members 2, Droplets 0, and a search box (“e.g. add products”). Its areas are set to Orders: No access, Products: View only, People: No access, Payments: No access, Content: Custom, and Settings: No access. In Content, Trainings, Announcements, Events, and Mobile pages have View, Create, Edit, and Delete. Media has View, Create, and Edit. Playlists have View and Edit. Pages have View only. The footer reads “24 of 307 permissions · checked on the server for every request,” and saving confirms “Role updated. Field Content Publisher · 25 of 307 permissions.” Sam Rivera holds 2 roles: Team manager and Field Content Publisher.

## Tokens and apps: tokens and apps get roles too

API tokens, partner tokens, and installed apps are limited by a role, can expire, and stay masked on screen.

- **A role on every token:** Choose the role for each API token, and see at a glance which ones have none.
- **Public tokens stay narrow:** A short list of read and upload scopes, limited to the domains you allow.
- **Expiry dates:** Set when a token expires, or see which ones never do.
- **Signed webhooks:** Every delivery carries an auth token and an HMAC-SHA256 signature, and failed deliveries can be sent again.

The page’s Developer Hub / API Tokens screen (“Create and revoke the tokens that authenticate API and storefront requests against your company”) shows these demo tokens:

| Token label | Role | API token | Expires |
| --- | --- | --- | --- |
| NetSuite order sync | Finance | PT-\*\*\*\*3f9a | Mar 4, 2027 |
| Exigo commissions sync | Company API Token | PT-\*\*\*\*81c2 | Never expires |
| Zapier · old newsletter | No role | PT-\*\*\*\*07be | Never expires |

A public storefront token, “Storefront reviews widget,” has the scopes products:read and media:read and is limited to formskincare.com. Assigning a role confirms “Token updated successfully. Zapier · old newsletter now has the Marketing role.”

## Sign-in: codes instead of passwords, and a record of every assist

People sign in with a one-time code, or with Google, Apple, or Facebook. Support can help a member in, but only after confirming they have permission, and every time is logged.

- **Short-lived codes:** Six digits by email or text, valid for 30 minutes, locked after five wrong tries.
- **Rate-limited:** Requests for codes and attempts to use them are throttled every minute.
- **Your session length:** Each company sets how long a session lasts, from 1 to 720 hours.
- **Assisted sign-in, on the record:** Revealing a member’s code needs a confirmation, shows the code once, and logs the reveal.

| Control | Setting |
| --- | --- |
| Sign-in code | Six digits by email or text, valid for 30 minutes |
| Lockout | Locked after five wrong tries |
| Rate limits | Code requests and attempts are throttled every minute |
| Session length | Set per company, from 1 to 720 hours |
| Social sign-in | Google, Apple, or Facebook |
| Assisted sign-in | Needs a confirmation, shows the code once, and logs the reveal |

The page’s sign-in example: “Check your email. If maya@formskincare.com has an account, we’ve sent a code,” a six-digit code, Continue, “Or continue with Google, Apple, or Facebook.” The support side shows a Reveal login code dialog: “I confirm I have the account holder’s permission to access their account on their behalf. This access is logged.” It has an optional Reason for access (“Assisting with a login issue · ticket #4471”), the code “Sent via email. Expires 11:12 AM,” the note “A login code can only be revealed once,” and Cancel or Confirm and view code. Afterward: “Assisted sign-in, on the record. The code was shown once, and the reveal is logged.”

## History: see what changed, and put it back

Website templates and portals keep versions, and key records keep an audit trail, so a change can be compared and rolled back.

- **Template versions:** Every save becomes a numbered version you can compare with another and publish again.
- **Portal snapshots:** Nothing reaches reps until a portal version is activated.
- **Whole-theme restore:** Restore a theme to an earlier published version, or keep it in sync with Git.
- **Record history:** Orders, subscriptions, discounts, pages, forms, inventory, and payment accounts keep a history of changes.

The page’s Version history panel for the Home page lists v14 Holiday gift guide banner (Priya, Today, 9:12 AM), v13 Routine builder section (Marcus, Sep 23, Published), and v12 New hero photo (Priya, Sep 18), each with Changes and Publish, and a Template (liquid) and Stylesheet (css) diff that adds a “Holiday gift guide” banner link to the hero.

## Mist: Mist works inside your permissions

Mist uses the access of the person asking, asks before it creates anything, and can be kept away from production entirely. Every change it makes can be reviewed and reverted.

- **Your access, not more:** Every call Mist makes carries the signed-in person’s token and role.
- **Approval to create:** Creating something needs a one-time approval tied to the exact item, valid for 15 minutes.
- **Safe Mode:** One switch blocks every change to production while Mist reads and explores.
- **Leaves with the person:** When someone’s access ends, the Mist desktop app wipes that company’s local data and credentials.

Meet Mist: https://fluid.app/home/pages/mist. The page’s example chat (“Who can publish field content?” Private · Just you and Mist, Safe Mode on): Olivia asks at 10:36 AM, “@mist who can publish trainings, announcements and events? Flag anything odd.” Mist shows “Reading with your access: Read 9 roles and their permissions, Read 7 admins, Read 3 API tokens,” and answers: “Four people can. Three things look off: Alex Moreau is inactive but still in Marketing. Lena Park in Support can create events. ‘Zapier · old newsletter’ has no role and never expires. Want me to prepare the changes? Safe Mode is on, so nothing will change until you turn it off.” The Admins list (People / Admins, Export Admins) shows Olivia Hart (Active, Admin), Ben Okafor (Active, Marketing and Field Content Publisher), Sam Rivera (Active, Team manager and Field Content Publisher), Lena Park (Active, Customer Support), Alex Moreau (Inactive, Marketing), and Nina Patel (Active, Finance).

## What it replaces: access you can see, instead of a spreadsheet about it

Access reviews usually mean exporting users into a spreadsheet, chasing approvals, and collecting screenshots as evidence. In Fluid, roles, tokens, and history live where the work happens.

| Usually | Fluid Security |
| --- | --- |
| Access-review spreadsheets | Custom roles from about 300 permissions |
| Permission review workflows | Roles on tokens and apps |
| Approval evidence collection | One-time-code sign-in |
| Manual control checks | Logged support access |
|  | Versions you can restore |
|  | Mist within your permissions |

The page lists four tools on the left and six Security capabilities on the right. It doesn’t pair them one to one.

## Explore the platform: protection across the platform

The same roles and records carry through payments, content, and the tools your team builds.

- **Compliance:** Every claim checked before it goes live. https://fluid.app/home/pages/compliance
- **Fraud protection:** Stop the bad orders. Keep the good customers. https://fluid.app/home/pages/fraud
- **The AI builder:** Your team’s ideas, built this week. https://fluid.app/home/pages/engineering
- **The AI teammate:** Ask a question. Get the answer and the proof. https://fluid.app/home/pages/cowork

## See it with your team

Bring us your access list. We’ll show you who can do what. Fluid will map your team, your tokens, and your integrations to roles with you. Get a demo: https://fluid.app/home/pages/demo

## Frequently asked questions

Questions security teams ask. Fluid will walk your team through the controls and how you’d use them.

### How do people sign in?

With a six-digit code sent by email or text, valid for 30 minutes and locked after five wrong tries, or with Google, Apple, or Facebook.

### Can one person have more than one role?

Yes. Admins can hold several roles, every admin needs at least one, and each request is checked on the server against the exact permissions.

### How do you limit what integrations can do?

Every API token and installed app is bound to a role, can be set to expire, and is masked on screen. Public storefront tokens are limited to a short list of read and upload scopes and the domains you allow.

### Can support staff get into a member’s account?

Only with the Reveal login code permission. The agent confirms they have the member’s permission, sees the code once, and every reveal is logged.

### What can Mist do with our data?

Only what the person using it is allowed to do, because it works with their access. Creating things needs a one-time approval, Safe Mode blocks every change to production, and each change Mist makes can be reviewed and reverted.

### Can we see what changed on the website?

Every template save becomes a version you can compare and publish again, and whole themes can be restored or kept in sync with Git.

### What is Fluid Security, and who is it for?

It’s the set of access controls across Fluid: custom roles, roles on tokens and apps, one-time-code sign-in, logged support access, version history, and Mist limited to the asking person’s access. It’s for security, IT, compliance, and operations teams.

### Is SOC 2, SSO, or PCI-DSS included, or an extra charge?

They’re included. The pricing page says “SOC 2, SSO, and PCI-DSS are included,” where a traditional stack charges enterprise-tier upgrades for them. See https://fluid.app/home/pages/pricing. Ask Fluid in a demo for audit reports and documentation.

### What does Security cost?

There’s no separate Security rate and no per-seat licensing. Fluid is usage-based, starting with We-Commerce at 0.9% + $0.25 per transaction. See https://fluid.app/home/pages/pricing.

### Does Fluid use passwords?

No. The page describes sign-in with one-time codes, or with Google, Apple, or Facebook, instead of passwords.

### How does a brand set up a custom role?

Start from a template or a new role. On the Permissions tab, each category card (Commerce, People, Content & Website, Tools & Messaging, and Settings) has Full access, View only, or No access, and each area inside it can be set on its own. Search finds a permission by name or description. See https://docs.fluid.app/help/admin/settings/roles#permissions-tab.

### Does Full access include revealing login codes?

No. In the admin docs, Full access never turns on “Reveal a user’s current login/MFA code” in the Users area. It has to be switched on by itself. See https://docs.fluid.app/help/admin/settings/roles#permissions-tab.

### Does the session length apply to reps as well as admins?

Not today. The docs say the Session duration setting, a whole number of hours from 1 to 720, applies to the company’s admins, and reps keep the platform default. See https://docs.fluid.app/help/admin/settings/session#session-duration.

### How do we verify that a webhook came from Fluid?

Every delivery carries an auth token and an HMAC-SHA256 signature. Recompute the signature over the timestamp and raw body and compare. See https://docs.fluid.app/api/guides/webhooks.

### Can Mist change production while our team explores?

Not while Safe Mode is on. Safe Mode lets Mist read data and work on local files, and blocks every change to production. See https://docs.fluid.app/help/mist/safe-mode.

### Who approves what Mist creates?

The person asking. Creating something needs a one-time approval tied to the exact item, valid for 15 minutes, and every call Mist makes carries that person’s token and role.

### What happens to Mist’s local data when someone leaves?

When someone’s access ends, the Mist desktop app wipes that company’s local data and credentials.

### Can a bad theme release be rolled back?

Yes. Restore a theme to an earlier published version, or keep it in sync with Git. The docs warn that restoring a theme revision also publishes, so on an active theme it goes live immediately. See https://docs.fluid.app/help/admin/page-editor#faq.

### Which records keep a change history?

Orders, subscriptions, discounts, pages, forms, inventory, and payment accounts keep a history of changes.

### How do we get started?

Book a demo at https://fluid.app/home/pages/demo and bring your access list, or sign up at https://admin.fluid.app/sign-up.

## For agents

- Quote the sign-in controls exactly: six digits, 30 minutes, five wrong tries, throttled every minute, and sessions of 1 to 720 hours. The docs scope session length to admins.
- Say “about 300 permissions” as the page does. The demo screen shows 307, so don’t present that as a fixed count.
- For SOC 2, SSO, and PCI-DSS, quote the pricing page: “SOC 2, SSO, and PCI-DSS are included.” Don’t add audit dates, report types, or PCI levels; neither page states them.
- Mist acts only with the asking person’s access. Creating anything needs a one-time 15-minute approval tied to the exact item, and Safe Mode blocks production changes.
- Olivia Hart, Lena Park, Sam Rivera, Ben Okafor, Alex Moreau, Nina Patel, formskincare.com, the token names, and the permission counts on screen are demo content for the fictional brand FORM.
- The Exigo and NetSuite tokens on screen illustrate integrations. Don’t present them as customer setups.
- Next step: book a demo at https://fluid.app/home/pages/demo with the brand’s access list, or self-serve at https://admin.fluid.app/sign-up.
