Monitor Status (Sidebar)

Status Controller – Full Detailed Description
 


1. What is the Status Controller really?
 

The Status Controller is a central control panel for tracking clients and their progress across multiple statuses, stages, or checkpoints, all on one screen.
 

Instead of opening each client separately, the Status Controller displays many clients together in a structured grid. Each client 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 clients are

  • Who is responsible for them

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

  • How these statuses change over time (on a monthly/yearly basis)
     

This is not just a report displaying data — it's an interactive dashboard where users can actively update statuses directly in the table.
 



2. Core Idea and Mental Model
 

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

  • Rows = Clients

  • Columns = Status Dimensions (sales pipeline stage, approval status, follow-up status, custom tag, etc.)

  • Cells = Actual Status Values, often color-coded and clickable
     

Each cell answers a simple question:
 

"For this client, what is the current status in this category?"


Users don't need to open client 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

  • Viewing many clients 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

  • Client onboarding stages

  • Compliance or execution tracking

  • Monthly progress tracking or follow-up control

  • Internal team responsibility 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 pop-up or modal.

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

Access rules:
 

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

  • Only administrators 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 header at the top including the current month and year, immediately clarifying that this view is time-based.
 

Below that:
 

  • Month selector

  • Year selector

  • Search field for quickly finding clients
     

The main area is a wide grid:
 

  • The first column is always Client Name

  • The second column is always Responsible Person

  • Then come up to 10 configurable status columns
     

Each column header represents a status category defined in the settings.
 


6. Client Rows and Responsibility
 

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

The Responsible Person column:
 

  • Displays the team member(s) linked to the client

  • Reflects sharing rules (shared_with)

  • Helps managers instantly see ownership and responsibility
     

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


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

Each configurable column represents a status type.

Examples:
 

  • Sales stage

  • Execution status

  • Approval status

  • Custom tag group

  • Internal review stage
     

Within each cell:
 

  • A status label is displayed (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 data updating fast and intuitive.
 


8. Time-Based Behavior (Month and Year)
 

A critical concept in the Status Controller is that status values are time-bound.
 

This means:
 

  • Statuses are saved per client, per column, per month

  • Changing the month/year displays a different snapshot

  • Historical progress can be reviewed by switching months
     

This is especially powerful for:
 

  • Monthly tracking

  • Performance comparison

  • Progress auditing

  • Reporting trends over time
     


9. Search and Filtering
 

The search input filters clients in real-time:
 

  • By client name

  • By related identifiers (depending on implementation)
     

This is particularly useful when working with large folders.
 

Pagination controls like Load More or Load All prevent performance issues while providing access to the entire dataset.
 


10. Settings and Configuration (High-Level)
 

The gear icon opens the Status Control Settings, where the structure of the Status Controller is defined.
 

From the settings, administrators can:
 

  • Select which folder feeds clients to the controller

  • Define up to 10 columns

  • Assign tags to columns

  • Configure status options for each tag

  • Choose colors and behaviors
     

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

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


11. How Data is Stored and Used
 

Behind the scenes:
 

  • Column definitions are in the status configuration table

  • Client-status values are saved in cus_status
     

  • Each record links:
     

    • Client

    • Status column

    • Selected status

    • Month and year
       

This design allows for:
 

  • Fast loading

  • Historical views

  • Clean separation of 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 the "Responsible Person" column to follow up with the right individual
     

No further navigation is needed.
 


13. Why the Status Controller is Powerful
 

The Status Controller is powerful because it:
 

  • Replaces dozens of separate lists and reports

  • Makes progress immediately visible

  • Reduces clicks and context switching

  • Adapts to various business processes

  • Supports both overview and detail editing
     

It's not just a report — it's a live operational dashboard.
 


14. Connection to Other Modules
 

  • It complements client lists, not replaces them

  • It works alongside tasks and automations

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

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


15. Summary (In Simple Terms)
 

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

  • See all clients

  • Track progress across multiple dimensions

  • Update statuses quickly

  • Work month by month

  • Stay coordinated as a team
     

It transforms client data into actionable visibility.

information_img