Modules

Sidebar: Modules — the fixed row at the bottom of the sidebar, just above Settings. The counter beside it shows how many modules are active out of those available to your account: 3/10 means three of ten.

FlyB is several products in one account: an inbox, a CRM, a booking engine, a landing page builder, an e-mail platform, a checkout. Most businesses use a few of them. Modules let each organization switch on exactly the parts it uses — and the whole dashboard follows: the menu lists only the screens of active modules, and the options that belong to a module that is off disappear from every other screen too. A form stops asking for a CRM stage when there is no CRM; the contact record stops showing a Bookings tab when there is no scheduling.

Always available

Some screens are the platform itself rather than a module, and every account has them:

• Dashboard, Analytics and Contacts
• Settings, Modules and the Ctrl + K search

The modules

The limits inside each module — how many calendars, pages or e-mails a month — are those of your plan, as before: see Plans, Flights & Limits. Every module’s Learn more lays them out plan by plan.

Forms are not a module of their own. A form is how a page, a blog, a FlyB Chat window, a QR Code or a CRM capture turns a visitor into a contact, so the Forms screen is shown while any of Landing Pages, Blogs, CRM, Inbox or Links & QR Codes is active.

Booking distribution links — one link sharing bookings between several calendars — are a link type of Links & QR Codes over the calendars of Scheduling, so they are offered when both modules are active.

Paid bookings — a calendar that charges one of your prices before confirming a booking — are a setting of Scheduling that sells through Sales with Stripe: the calendar editor offers it while Sales with Stripe is active. A calendar already charging keeps charging, and keeps showing the setting, if the module is switched off. See Charging for bookings.

The Modules screen

All modules are shown together, one card each. Active modules are outlined in their own colour, so they stand out from the rest. A module that is not on every plan carries a badge naming the plans that include it — with a lock when yours is not one of them. Each card has two buttons:

• Learn more opens the module’s full description: what you can do with it, what it adds to your menu, what each plan includes, what it needs and what it pairs well with, and a link to its chapter of this manual. Clicking the module’s icon or name opens it too.
• Activate switches it on. An active module shows Open instead, which takes you to its first screen — except WhatsApp and Sales with Stripe, which show Manage while your plan includes them and take you to Settings → Integrations, where their connections are made.

The filters at the top show all modules, only the active ones, or only those you have not switched on yet.

Activating a module

• Who. Only the organization’s owner and its admins. Every member can open the Modules screen and read Learn more; for anybody else the Activate button is disabled and says who can use it.
• Plan. A module your plan does not include shows Upgrade instead of Activate. Subscribing to Plus or Prime also enables WhatsApp Web on the account, as soon as the payment is confirmed — activate the WhatsApp module and connect a number from Settings → Integrations.
• Requirements. WhatsApp works inside the Inbox, so activating WhatsApp while the Inbox is off asks you to confirm and switches both on together.
• Right away. The module’s screens appear in the menu as soon as you activate it.

Deactivating a module

Owners and admins deactivate a module from the ⋯ menu on its card or from its Learn more. The confirmation says exactly what leaves the menu and what keeps running.

Deactivating hides; it never deletes, unpublishes or stops anything:

• published pages, blogs, booking pages, pricing tables and QR Codes stay online;
• scheduled campaigns, message automations, stage automations and booking reminders keep sending — pause them first if you want them to stop;
• your data stays exactly where it was, and reactivating brings everything back as it was.

Deactivating the Inbox also deactivates WhatsApp, which needs it.

Inside other screens, the options of a module that is off are hidden — with one exception: a setting that is already in use stays visible, so it can still be seen and changed. A form that sends its leads to a CRM stage keeps showing the stage picker even after the CRM is switched off, because the published form keeps honouring it.

A bookmark or a link to a screen whose module is off shows that module’s card, with the button that activates it (or the name of who can).

If your plan changes

An active module that your new plan does not include stays active, marked Not in your plan on its card. Nothing disappears from your menu; the module’s screens apply their own plan limits, as they always did, and upgrading lifts them again.

Your first access

A new account starts with the Inbox, the CRM and Scheduling active, and its first visit to the dashboard opens the Modules screen with a welcome: choosing the modules is the first decision a new account makes — switching on what it will use, and off any of those three it will not.

If you signed up from something you had already started on flyb.app, the matching module is switched on for you and you land exactly where you left off:

Accounts created before modules

When modules were released, every existing account kept everything it used: the Inbox and the CRM were switched on for all accounts, and every other module was switched on wherever the account already had something of it — a page, a calendar, a blog, a campaign or template, a WhatsApp number, a plan or pricing table, a link, an affiliate record. AI Creatives was switched on for every account with a paid subscription. Only the modules an account had never used were left off, ready to be activated.

The menu

The sidebar keeps its groups, but a group with a single entry — because the other screens of that group belong to modules that are off — is shown as that entry on its own, so it never costs an extra click.

Team permissions

Modules decide what the organization uses; permissions still decide what each member may do in it. On Settings → Team, the permission grid lists only the rows of modules that are active. Any customisation you made to a member is kept while a module is off and applies again when it is reactivated.

The Public API is not affected by modules.