The operational workspace

The control area is WBAMS's authenticated operating surface. It brings customer context, billing, plans, orders, support, content, reporting, automation, integrations, and system configuration together under /control.

Customers

Profiles, users, contacts, services, invoices, transactions, tickets, email, and activity.

Billing

Invoices, payments, transactions, credits, quotes, and gateway operations.

Support

Helpdesk tickets, departments, knowledgebase articles, updates, and downloads.

Content

CMS pages, menus, media, page-builder sections, theme settings, and search metadata.

Insights

Operational, customer, income, forecast, performance, and feedback reports.

System

Automation, storage, integrations, security, logs, health, and configuration.

Roles and permissions

Create roles around real responsibilities. Grant only the capabilities required, test the role using a non-super-admin account, and keep at least two recoverable administrator accounts. Review access after staffing or ownership changes.

Custom control directory

The shipped directory is control. If you rename it, update the configured control path, web-server rules, scheduled links, monitoring, and bookmarks as one change. The PHP view directory remains resources/views/control; it is a code namespace, not the public URL folder.

Do not expose diagnostics

Remove temporary probes, development scripts, installers, and database exports from the public application tree after use.