Customer setup needed
This capability depends on customer-approved providers, devices, credentials, or operational readiness before it is treated as live.
Provider setup
Payment gateway, SMS, WhatsApp, printer, courier, storage, device, and delivery integrations using customer-approved provider setup.
A module page should show the buyer what the module does, how it looks or flows, which facilities are included, where the workspace opens, and what must be ready before live use.
Name, workspace module, short summary, availability, and setup CTA.
Live screenshots from Admin Gallery or a workflow visual when live proof is pending.
The exact facilities a buyer can understand before setup starts.
Where the customer works after access, role, and subscription are ready.
Packs, owner modules, workflow steps, boundaries, and rollout checks.
Explains how generated financial impact moves through tax, payment, posting, ledger, and audit checks.
This capability depends on customer-approved providers, devices, credentials, or operational readiness before it is treated as live.
These are the facilities a buyer can understand before setup. The actual workspace shows only the menus and actions allowed for the organization, selected plan, and user role.
Enabled through BPT setup and shown to the right users when the organization is ready.
Enabled through BPT setup and shown to the right users when the organization is ready.
Enabled through BPT setup and shown to the right users when the organization is ready.
Enabled through BPT setup and shown to the right users when the organization is ready.
This page keeps the public message simple: what this capability does, when it can be enabled, and which workspace the customer uses after setup.