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, or under the address of its own you gave it.

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.

The red counts on Orders, Billing and Support name themselves on hover — "7 overdue invoices", "2 pending orders", "2 tickets awaiting reply" — and the same count appears on the item it comes from once the section is open: Billing › Invoices › Overdue, Orders › Pending Orders, Support › Support Tickets. Under Help Center, Updates opens to All updates and Settings, and Knowledgebase to Articles and Settings. Since 1.11.0 admin pages open in their final layout rather than drawing an older header first and then jumping.

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.

The admin area's address

The admin area ships in the control folder, at https://example.org/control/. A name only you know keeps sign-in attempts away from it. The easiest moment to choose one is the end of setup, whose last page offers it (Install WBAMS). Later, it is set in settings.php:

  1. Choose a nameof three to sixty-four letters, numbers, hyphens or underscores, in lower case. It must not be something already at the top of the site, nor an address the website uses for its own pages, such as account, knowledgebase, products, book or install.
  2. Name it in settings.phpwith the line $customadminpath = 'your_address';.
  3. Sign in at the new addressand bookmark it. Change the bookmarks, monitoring checks and any web server restriction that named /control/.

Every admin page, its stylesheets, scripts and links follow the address, and updates keep it. To go back to /control/, remove the line.

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.