Status Controller – Settings

Status Controller – Settings (Full Detailed Explanation)
 

1. What These Settings Control (Big Picture)
 

The Status Controller settings define the entire structure of the Status Controller page.
 

Nothing you see on the Status Controller grid happens automatically — everything is driven from here.
 

From these settings, an admin decides:
 

  • How many status columns exist (up to 10)

  • What each column is called

  • Whether a column is static or dynamic

  • Which tag the column is linked to

  • How the column behaves over time (monthly, bi-monthly, or fixed month)

  • Which statuses are available in each column

  • What colors, dates, or values each status supports
     

In short:
 

This settings area defines the logic, behavior, and visual meaning of the Status Controller grid.


2. Where the Settings Live and Who Can Access Them
 

The Status Controller settings are part of the Admin Settings area.
 

They appear under a dedicated tab called “Status control”.

This tab is not visible to normal users.
 

Only the following users can access it:
 

  • Organization admins

  • Users with the explicit permission to manage Status Controller settings
     

This ensures that:
 

  • Regular users only use the Status Controller

  • Only trusted users can change its structure
     

3. The Column Selection Screen (Starting Point)
 

When the Status control tab opens, the admin sees a clear instruction:
 

“Select a column to open its settings.”


Below this text are up to 10 column slots.
 

Each slot represents one column that can appear on the Status Controller page.
 

At this point:
 

  • Columns may already have names (from previous configuration)

  • Or they may show default placeholders (Column 1, Column 2, etc.)
     

Clicking any column opens a dedicated configuration modal for that column.
 

Each column is configured independently.
 


4. The Column Configuration Modal (3-Step Flow)
 

Every column has a three-step setup flow, shown clearly at the top of the modal:
 

  • Step 1 of 3 – Column settings

  • Step 2 of 3 – Tag settings

  • Step 3 of 3 – Status settings
     

The user always knows:
 

  • Where they are

  • What comes next

  • What has already been configured
     

5. Step 1 – Column Settings (Identity & Behavior)
 

This step defines what the column is.
 

Column name
 

The first and most important input is the column name.
 

This is the header text that appears at the top of the Status Controller grid.
 

Admins use this to give business meaning, such as:
 

  • Sales Stage

  • Execution Status

  • Follow-up Phase

  • Approval Step
     

This name is mandatory because:
 

  • The column cannot exist without a visible identity

  • It ensures clarity for all users viewing the grid
     

Static column option
 

Below the name is the Static column checkbox.
 

When enabled:
 

  • The column is treated as fixed

  • Its behavior does not change dynamically across time or logic

  • Backend logic may use this flag to treat the column differently
     

This is useful for columns that:
 

  • Represent permanent attributes

  • Should always be visible

  • Should not rotate or vary by time rules
     

Saving Step 1
 

When the admin clicks Update, the system immediately saves:
 

  • The column name

  • The static flag
     

This ensures the column has a valid identity before moving forward.
 

6. Step 2 – Tag Settings (Meaning & Time Logic)
 

This step defines how the column behaves logically.
 

Tag selection
 

Each column can be linked to one tag.
 

Tags act as:
 

  • Logical groupings

  • Filters

  • Metadata that connects this column to other system logic
     

For example:
 

  • A “Sales Stage” column might use a “Pipeline” tag

  • A “Follow-up” column might use a “Reminder” tag
     

This association allows:
 

  • Consistent filtering

  • Better reporting

  • Structured data relationships
     

Type (time behavior)
 

Next, the admin chooses how this column behaves over time.
 

There are three behaviors:
 

  • Monthly – value changes month by month

  • Bi-monthly – value spans two months

  • Specific month – value is tied to one fixed month
     

This setting directly controls:
 

  • How the column behaves when users switch months

  • Whether historical tracking is enabled

  • Whether the column is time-locked
     

Specific month (conditional)
 

If “Specific month” is selected:
 

  • A month selector appears

  • The admin chooses exactly which month this column applies to
     

This is useful for:
 

  • One-time campaigns

  • Seasonal tracking

  • Fixed reporting periods
     

Saving Tag Settings
 

Clicking Update saves:
 

  • The tag

  • The time type

  • The month (if applicable)
     

The column now has meaning and time logic.
 

7. Step 3 – Status Settings (What Users Can Select)
 

This is the most important step because it defines what users can actually choose in the grid.
 

Status name
 

Each status is a selectable option that users see in the Status Controller cells.
 

Examples:
 

  • Not Started

  • In Progress

  • Completed

  • Blocked

  • Approved
     

Admins can add multiple statuses per column.
 

Color
 

Every status has a color.
 

Colors are critical because:
 

  • Users scan the grid visually

  • Status meaning is recognized instantly

  • Problems and progress stand out immediately
     

For example:
 

  • Red for blocked

  • Yellow for in progress

  • Green for done
     

Date or value behavior
 

A status can optionally require extra input.
 

The admin can choose:
 

  • Date – user must select a date when applying this status

  • Value – user must enter a numeric value
     

This enables advanced use cases like:
 

  • Completion date tracking

  • Amount tracking

  • Score or quantity tracking
     

Saving statuses
 

When clicking Update:
 

  • The status is added to the column

  • Color and date/value rules are saved

  • The system validates that the column name exists
     

If the column name is missing, the system:
 

  • Stops the save

  • Sends the admin back to Step 1

  • Prevents broken configuration
     

8. Managing Existing Statuses
 

After statuses are added:
 

  • They appear in a list inside the modal

  • Admins can edit or delete them

  • Status order can be changed by dragging
     

The order matters because:
 

  • It controls dropdown order

  • It affects how users think about progression
     

9. Navigation and Completion
 

At any point:
 

  • The admin can go Back to previous steps

  • Changes are saved step-by-step

  • Clicking Done closes the modal
     

Once closed:
 

  • The Status Controller page immediately reflects the changes

  • No page refresh is needed
     

10. How These Settings Affect the Status Controller Page
 

After configuration:
 

  • Columns appear with the chosen names

  • Status dropdowns show the defined options

  • Colors render correctly

  • Date/value prompts appear when required

  • Month behavior works as defined
     

Users never see the complexity — only a clean, powerful grid.
 

11. Why This Design Is Powerful
 

This 3-step configuration ensures:
 

  • Clear separation of concerns

  • No accidental misconfiguration

  • Maximum flexibility

  • Scalability for different business models
     

Admins can adapt the Status Controller to:
 

  • Sales pipelines

  • Project execution

  • Customer onboarding

  • Compliance tracking

  • Any custom workflow
     

12. Plain-Language Summary
 

The Status Controller settings are the brain behind the Status Controller page.
 

They let admins:
 

  • Define columns

  • Attach meaning

  • Control time behavior

  • Create visual, interactive statuses
     

Once configured, users get a fast, intuitive workspace without ever touching settings.


 

information_img

מוצרים

מודולים

מאפיינים

מחירון

עלינו

צרו קשר

עוד

BIZ1 CRM
באינטרנט
איש קשר Biz1.co.il