Login Mode
Choose which authentication methods users can use. Changes apply immediately, no restart.
This page is being opened using file://. GT Table must be served from
http://localhost:3001 so API routes work.
Start the backend:
cd server && npm start
Open http://localhost:3001/ after starting the server.
Zashpal Retail
VM gandola & GT operations sheet
Username ya password galat hai.
Operations Sheet
Data Input
Central Feeder
Master Control
| Name | Username | Mobile | Role | Store | Status | Live | Last Login | Sessions | Created | Updated | Actions |
|---|
| Name | Role | Live | Sessions | Last Login |
|---|
Role distribution loads after user list refresh.
Permission enforcement is configured per user in Edit User.
Audit trail is captured for user management actions.
Team assignments and store groupings can be managed from this workspace.
Security policies, lockouts, and session controls are summarized here.
Recent user activity and login patterns appear here.
Communication & Authentication
Choose which authentication methods users can use. Changes apply immediately, no restart.
Operational OTP settings. Login ends only when the user logs out or closes the tab/browser.
Select a WhatsApp provider, store encrypted credentials, and test connectivity. GT Table keeps its own independent settings.
Master Control
Rename runtime field labels used in the operational table.
KH/BJ threshold and label configuration.
Column mapping rules for feeder uploads.
Recent system engine changes with restore support.