View 1: Settings Interface – Tab Creation
Complete Administrative & Configuration-Level Description
Overview
The Settings Interface is the administrative control panel where Tab templates are created, configured, and maintained.
This interface represents the foundation layer of the Tabs system.
Everything related to tabs—customer data entry, filtering in the header, automation triggers, API usage, and reporting—depends entirely on how a tab is defined in this interface.
At this level:
-
No customer data is created
-
No records exist yet
-
Only the structure, rules, and behavior of tabs are defined
Because of this, the Settings Interface is used only by administrators and plays a critical role in system stability and data consistency.
Location and Access
The Tab Creation interface is located inside the Admin Settings area.
-
URL Path:
dashboard/admin/settings→ Tab Settings
Access Rules
Only users who meet all of the following conditions can access this interface:
-
Organization owner or admin role
-
Permission to access system settings
-
Permission to create or modify tabs
This restriction ensures that tab definitions remain centralized and controlled.
Purpose of the Settings Interface
The Settings Interface exists to allow administrators to:
-
Define custom business modules (Tabs)
-
Control where tabs appear in the system
-
Define structured data collection rules
-
Configure workflows using statuses and sub-statuses
-
Assign access permissions
-
Prepare tabs for automation and API usage
In simple terms:
The Settings Interface defines how a tab behaves everywhere else in the system.
Structure of the Tab Creation Interface
The tab creation form is divided into five logical sections, each responsible for a specific aspect of tab behavior.
1. Basic Tab Information
(Identity & Scope Definition)
This section defines what the tab is and where it is allowed to exist.
Tab Identity
-
Administrators provide tab names in English and Hebrew
-
Names are used consistently across:
-
Settings
-
Header navigation
-
Customer profile view
-
API mapping
-
A system-safe identifier is automatically generated from the English name and used internally.
Folder Assignment
-
One or more folders must be selected
-
The tab will only appear for customers that belong to these folders
-
This prevents irrelevant tabs from appearing for the wrong customer type
Folder assignment is mandatory because it defines the scope of the tab.
2. Status Configuration
This section defines how records inside the tab move through stages.
Administrators configure:
-
Main statuses (e.g., New, In Progress, Completed)
-
Optional sub-statuses for each main status
-
Colors for visual clarity
-
Column titles for multilingual display
Why Statuses Matter
Statuses are not cosmetic.
They control:
-
Filtering logic
-
Automation triggers
-
Reporting
-
Visual indicators in the UI
Each status:
-
Has a unique internal ID
-
Has a display label
-
Can contain multiple sub-statuses
This allows tabs to behave like pipelines, workflows, or process trackers.
3. Sharing and Permissions
This section defines who can see and use the tab.
Administrators can:
-
Share the tab with all team members (default)
-
Restrict the tab to selected users only
If no users are explicitly selected, the tab remains visible to all team members.
This ensures:
-
Sensitive tabs can be restricted
-
Operational tabs can be shared
-
Access control remains flexible
4. Display & Behavior Settings
(System Integration Rules)
This section controls how the tab integrates with other parts of the system.
Header Visibility
-
When enabled, the tab appears in the header
-
Users can click it to filter customers
-
When disabled, the tab appears only inside customer profiles
Tab Linking & Copying
-
Tabs can be linked to other tabs
-
Records can be copied automatically
-
Status changes can optionally sync between linked tabs
These options enable advanced workflows across multiple tabs.
5. Action Controls
(Save & Update Logic)
At the bottom of the form:
-
A Save button validates and submits the configuration
-
Hidden fields track whether the action is create or update
-
Existing tab definitions are updated in-place
Once saved:
-
The tab becomes active immediately
-
It is available system-wide
-
No customer data is created yet
Tab List (Management View)
Below the form, the interface displays a list of all existing tabs.
From this list, administrators can:
-
Edit a tab
-
Duplicate a tab
-
Add or modify custom fields
-
Delete a tab (with confirmation)
This list acts as the management dashboard for all tab definitions.
Custom Fields Configuration
Custom fields define what data is collected inside a tab.
Fields are added via a dedicated modal and support:
-
Text, number, date, time
-
Select and multi-select
-
Yes/No toggles
-
Team member selection
-
Customer reference
-
Files and attachments
-
Formula-based calculated fields
-
Section titles and dividers
Each field includes:
-
English and Hebrew labels
-
Required flag
-
Default values
-
Type-specific validation
Internally, all fields are stored as a JSON schema, allowing unlimited flexibility without database changes.
Saving and Processing Logic
When the form is submitted:
-
Client-side validation runs
-
Server validates permissions and data
-
Status structures are normalized
-
Folder and sharing data are processed
-
Field schemas are encoded
-
Data is inserted or updated in
tabs_setting
A successful save activates the tab instantly.
Final Conceptual Summary
-
Settings Interface = Blueprint
-
Tab Settings = Rules and structure
-
Tab Records = Actual customer data (created later)
Changing settings affects behavior, not existing data.
Final One-Line Understanding
The Settings Interface for Tab Creation is the administrative blueprint layer where tabs are defined, scoped, structured, and integrated before they are used anywhere else in the Biz1 system.
