Status Controller (sidebar)

Status Controller – Full Detailed Description
 


1. What the Status Controller Really Is
 

The Status Controller is a central control board for tracking customers and their progress across multiple statuses, stages, or checkpoints, all in one screen.
 

Instead of opening each customer one by one, the Status Controller shows many customers together in a structured grid. Each customer appears as a row, and each configurable status category appears as a column.
 

This creates a powerful overview screen where users can immediately see:
 

  • Who the customers are

  • Who is responsible for them

  • What stage, state, or condition each customer is currently in

  • How those statuses change over time (month/year based)
     

It is not a report that only shows data — it is an interactive control panel where users can actively update statuses directly in the grid.
 



2. Core Idea and Mental Model
 

Think of the Status Controller as a spreadsheet-like status board, but fully connected to Biz1 logic.
 

  • Rows = Customers

  • Columns = Status dimensions (pipeline stage, approval state, follow-up state, custom tag, etc.)

  • Cells = Actual status values, often color-coded and clickable
     

Each cell answers a simple question:
 

“For this customer, what is the current status in this category?”


Users don’t need to open customer profiles or navigate away — everything is visible and editable inline.
 


3. Why the Status Controller Exists (Purpose)
 

The Status Controller exists to solve problems that traditional CRM lists cannot:
 

  • Tracking progress instead of static data

  • Seeing many customers at once, not one by one

  • Updating statuses quickly, without opening edit forms

  • Managing workflows that change over time (month by month)

  • Supporting custom business logic, not just predefined CRM stages
     

Typical use cases include:
 

  • Sales pipeline tracking

  • Customer onboarding stages

  • Compliance or execution tracking

  • Monthly progress or follow-up control

  • Internal team accountability views
     


4. Where the Status Controller Appears in the System
 

The Status Controller is a dedicated module, not a sub-view.
 

  • It appears as “Status controller” in the main sidebar navigation.

  • It opens as a full page, not a modal or popup.

  • It is accessible only if the module is enabled for the organization.
     

Access rules:
 

  • Regular users can view and update statuses (if permitted).

  • Only admins or users with Status control settings permission can change:

    • Which columns exist

    • Which tags/statuses are available

    • Which folders feed the controller
       

This separation ensures data safety and process consistency.
 


5. What You See When the Page Loads
 

When the Status Controller page opens, the user sees:
 

A large title at the top that includes the current month and year, making it immediately clear that this view is time-based.
 

Below that:
 

  • A month selector

  • A year selector

  • A search field to quickly find customers
     

The main area is a wide grid:
 

  • The first column is always Customer name

  • The second column is always Responsible

  • After that come up to 10 configurable status columns
     

Each column header represents a status category defined in settings.
 


6. Customer Rows and Responsibility
 

Each row represents one customer from a specific folder selected in Status Controller settings.
 

The Responsible column:
 

  • Shows the team member(s) linked to the customer

  • Reflects sharing rules (shared_with)

  • Helps managers instantly see ownership and accountability
     

This makes the Status Controller especially useful for team leads and managers.
 


7. Status Columns and Cells (The Heart of the Module)
 

Each configurable column represents a status type.

Examples:
 

  • Sales Stage

  • Execution State

  • Approval Status

  • Custom Tag Group

  • Internal Review Step
     

Inside each cell:
 

  • A status label is shown (often color-coded)

  • If no status is set, a placeholder like “Select status” appears

  • Clicking the cell opens a dropdown with available statuses
     

Statuses can include:
 

  • Simple labels (e.g. Pending, Done)

  • Colors for quick scanning

  • Optional date or value fields (depending on configuration)
     

This makes updating data fast and intuitive.
 


8. Time-Based Behavior (Month and Year)
 

A critical concept of Status Controller is that status values are time-scoped.
 

This means:
 

  • Statuses are stored per customer, per column, per month

  • Changing the month/year shows a different snapshot

  • Historical progress can be reviewed by switching months
     

This is extremely powerful for:
 

  • Monthly tracking

  • Performance comparison

  • Progress auditing

  • Reporting trends over time
     


9. Search and Filtering
 

The search input filters customers in real time:
 

  • By customer name

  • By related identifiers (depending on implementation)
     

This is especially useful when dealing with large folders.
 

Pagination controls like Load More or Load All prevent performance issues while still allowing access to full datasets.
 


10. Settings and Configuration (High Level)
 

The gear icon opens the Status control settings, which is where the structure of the Status Controller is defined.
 

From settings, admins can:
 

  • Choose which folder feeds customers into the controller

  • Define up to 10 columns

  • Assign tags to columns

  • Define status options for each tag

  • Choose colors and behaviors
     

Once configured, the Status Controller page automatically reflects those rules.
 

Users on the page never need to think about configuration — they only interact with the result.
 


11. How Data Is Stored and Used
 

Behind the scenes:
 

  • Column definitions live in the status configuration table

  • Customer-status values are stored in cus_status
     

  • Each record links:
     

    • Customer

    • Status column

    • Selected status

    • Month and year
       

This design allows:
 

  • Fast loading

  • Historical views

  • Clean separation between structure and data
     


12. How Users Typically Use the Status Controller
 

In daily work, users:
 

  • Open the Status Controller

  • Select the current month

  • Scan rows to see progress

  • Click cells to update statuses

  • Use colors to identify bottlenecks

  • Use Responsible column to follow up with the right person
     

No extra navigation is needed.
 


13. Why Status Controller Is Powerful
 

The Status Controller is powerful because it:
 

  • Replaces dozens of separate lists and reports

  • Makes progress visible instantly

  • Reduces clicks and context switching

  • Adapts to different business processes

  • Supports both overview and detail editing
     

It is not just a report — it is a live operational control panel.
 


14. Relationship to Other Modules
 

  • It complements Customer lists, not replaces them

  • It works alongside Missions and Automations

  • It often drives decisions that trigger follow-ups or tasks

  • It integrates naturally with Biz1’s folder-based structure
     


15. Summary (Plain Words)
 

The Status Controller is a smart, configurable grid that lets teams:
 

  • See all customers

  • Track progress across multiple dimensions

  • Update statuses quickly

  • Work month by month

  • Stay aligned as a team
     

It turns customer data into actionable visibility.

 

information_img