My Biz Flow

Help & Documentation

My Biz Flow is a modular, no-code, multi-vertical business/CRM platform. Businesses mix and match modules — POS, Service Centre, Billing, Clinic, HRMS, and more — on a single account, all built on one shared metadata engine. This page is a general orientation guide; it's visible to any signed-in user, not just admins.

See the full Module Guide → — every module, and what Basic/Pro/Ultimate unlocks for each.

The Partner & module concept

A company that signs up is a Partner. Partners don't pick a fixed business "type" from a list — they enable the modules relevant to how they operate. A repair shop might enable Service Centre + Inventory + Billing; a clinic might enable Clinic + Billing + HRMS. Each module owns its own records, fields, and pipeline, but they all share the same underlying platform.

Navigating the sidebar

The sidebar nav is grouped by taxonomy. An amber dot marks Brand / multi-location modules, a teal dot marks vertical business modules (the industry-specific ones like POS or Real Estate), and a neutral dot marks cross-cutting modules (Inventory, HRMS, Accounting) that plug into whichever vertical modules you're running. Click any module to land on its list page.

Create, Edit, and Delete

Every module follows the same pattern. The list page shows every record in a table with a "+ New" button top-right. Clicking a row opens that record's detail page, which shows Edit and Delete in its header. Edit reopens the same form pre-filled with the record's values; Delete asks for confirmation first, naming the record so you don't delete the wrong thing by accident.

FAQ

What is My Biz Flow?
A modular, no-code, multi-vertical business/CRM platform. Instead of shipping a separate product per industry, every business runs on one shared metadata engine — modules, fields, pipelines, and dashboards are all config-driven, and a business simply enables the modules it needs.
What is a Partner, and what does a module 'type' mean?
A signed-up company on the platform is called a Partner. A Partner doesn't have a fixed 'type' from a hardcoded list — its type is just the set of modules it has enabled (POS, Service Centre, Clinic, HRMS, and so on). Enabling or disabling a module changes what a Partner can do without changing any code.
How do I navigate the sidebar?
The sidebar groups modules by taxonomy: Brand (amber dot) for multi-location/partner hierarchy, Modules (teal dot) for vertical business modules like POS or Clinic, and Cross-cutting (neutral dot) for modules like Inventory or HRMS that plug into any vertical. Click a module to open its list page.
How does Create / Edit / Delete work?
Every module's list page has a "+ New" button that opens a create form. Clicking a row opens that record's detail view, which has Edit and Delete actions in the header. Edit opens the same form pre-filled with the record's data. Delete opens a confirmation dialog before anything is removed. In this pass there is no backend wired up yet, so Create/Edit/Delete are demo stubs — the UI and field coverage are real, persistence is a follow-up build.
How do I add a custom field?
Custom fields aren't editable from the UI yet in this pass. Every module's admin page (Super Admin only) is scaffolded as the future home for field/pipeline configuration — see a module's "Admin" section in the sidebar. Until that editor is built, field sets are defined in code per module and shown in the Designer.
What does a module's admin page do?
Each module has an admin/ subfolder gated to Super Admin. It's meant for no-code configuration of that module: custom fields, pipeline/workflow stages, and role permissions. It's scaffolded across all modules today; the actual field/pipeline editor UI is a follow-up build.
Who can access admin pages?
Admin pages (anything under a module's admin/ folder, plus platform tools like the Designer) are meant for Super Admins only. Auth/session enforcement isn't wired up yet in this pass, so admin pages show a visible warning banner instead of silently pretending to be protected — that keeps the gap honest until real auth lands.
What is the Designer, and why does every page register there?
The Designer (/admin/designer, Super Admin only) lists every page in the product, grouped by module, with a detail view per page showing its purpose and actual source code. Every page in the app calls registerPage() so it's guaranteed to show up there — a page that never registers is a page nobody can find or customize, which the design system treats as a bug.