Sign in with your username and PIN. Forgot your PIN? Ask the Admin — only the Admin can reset it.
Site Workspace
Dedicated Site Portal
No Features Activated Yet
The Master Admin has not activated any modules for this site yet. Ask the Admin to approve features in Multi-Site Profiles → Site Feature Approval Matrix.
Voucher Management & Manual Issue
Available Package
Price
Duration
Data
Live Vouchers & Usage Monitor
Voucher Code
Package
Remaining Time
Data Left
Status
Payment System & Paystack Checkout
Payment Check & Reference Verification
Data & Time Rollover
Omada Scan & Voucher Groups
Group
Unused
In Use
Expired
Payment Reconciliation & Order Approval
Reference
Plan
Amount
Status
Action
Confidence / Trust Score Verification
Approved Bot, VIP & Extension Modules
Dashboard
Center Manager v3.11.21
Sync: Active0 Errors
0
Active Sites
0
Voucher Groups
0
Live Vouchers
0
Total Orders
₦0
Paid Revenue
Needs attention
Checking...
Quick actions
Central Sync ready.
Rules Center · All system rules
All rules are gathered below. Scroll through the sections, edit any setting, then use Save ALL Rules. Automatic approval remains off unless you explicitly enable it.
0
Scans in 24 h
0
Matched to an order
0
Underpaid
0
Need your attention
Optional local AI runtime · Gemma 3 4B
Manual install only
Ollama starts without model weights. Gemma is never downloaded automatically. Install only when you explicitly press the button. The model is unloaded after use to release RAM. The fifth-scanner decision pipeline is not yet activated; payment approval rules remain unchanged.
Checking local AI runtime…
Installing the model does not turn on AI payment decisions. The AI scanner feature remains OFF until its evidence pipeline is implemented and tested.
Underpayment rules
Bank transfer rules
Leave auto-approve off until you have watched the scanners for a few days. Off = scans only match, flag and tell you; you approve in Reconciliation.
Payment system rules
Future rules
IF a fact about the payment meets a condition, THEN do something. Runs on every scan. Add as many as you like.
On
Name
Applies to
IF
Value
THEN
Note
Scanner 1 · Receipt scanner
Reads payment screenshots customers send you in private chats and answers them.
Scanner 2 · Bank alert scanner
Watches chats you choose for bank credit alerts, typed or as a picture.
Voucher issuance & stock rules
Editable controls for voucher delivery, duplicate protection, rollover and stock thresholds.
Voucher Rules
Control voucher issuance, code format, duplicate/underpaid order guards, rollover rules, and stock alerts.
Only contacts on this admin-managed list can roll over. The allowed window is fixed: 24 hours before expiry until 24 hours after expiry.
Central synchronization rules
Control how Omada, live usage and WhatsApp settings synchronize across this installation.
Central Sync Rule (System-Wide Interlock)
Every subsystem talks through this central rule so Omada stock, live voucher usage, orders, and ZimaBot WA stay in sync.
Payment confidence & trust rules
Edit every supported trust factor, its Light/Normal weights, and approval thresholds.
Confidence Approval
Email bank-credit alert rules
Edit mailbox access, receiving bank/account, sender filtering, polling frequency and SSL settings; test or poll the mailbox here.
Email Payments
Smart Email Scanner 2
Independent smart parser for Yahoo and any standards-based IMAP mailbox. It reads text and HTML, extracts transaction references and account evidence, scores confidence, and sends uncertain alerts to manual review.
Scanner health
Scanner status will appear here.
Recent bank credit alerts
Nothing read yet.
Save the complete Rules Center
This saves payment/scanner rules and all voucher, central-sync and confidence settings together. You can still use the section save buttons if needed.
Scanner status
Loading...
Recent scans
When
Scanner
From
Amount
Result
Order
Why
Nothing scanned yet.
WhatsApp command, bank-transfer & helpdesk rules
Bank details, customer permissions, command switches, menu text, keywords and helpdesk behaviour.
WhatsApp Settings (ZimaBot WA)
ZimaBot operating hours & message rules
Edit the schedule, away message, reply pacing, rate limits, opt-in/opt-out words and voucher-system link used by the WhatsApp bot.
Day
On
Opens
Closes
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Sunday
Advanced ZimaBot reply rules
These are the live WhatsApp reply rules stored by the ZimaBot engine. Edit the match words, reply text, alerts and timing here.
Editable automatic reply rules
On
Name
Match
Keywords
Reply text
Alert admin
Uses
Human takeover & escalation rules
Control when the bot hands a customer to a person, urgent-word escalation, after-hours wording and when control returns to the bot.
Save these settings
Saves this page together with the other Rules Center settings. Everything on this page is loaded when you open it, so nothing else is overwritten.
The bot works by polling Telegram, so no public address or webhook is needed. Send /start to your bot to learn your chat ID (several admins: separate with commas).
Import vouchers manually
Bring vouchers that already exist into Live Vouchers so their balance and usage are tracked. Codes already listed are skipped, so it is safe to import twice.
Code
Group
Time
Data
Status
Live Vouchers, Balance & Data Usage
Track remaining time, remaining data MB/GB, and live usage bars per voucher.
Inspect every logged error with its Error Code, module, timestamp, and details.
Error Code
Module
Message & Detail
Time
Action
Activity Stream
Themes & Skins
Choose a visual theme/skin and save it to your system settings.
Midnight Slate
Deep navy-slate dark mode with cobalt accents.
Emerald Zima
ZimaOS-inspired dark forest green with emerald highlights.
Royal Violet
Modern dark indigo-violet skin for low-glare screens.
Arctic Day
Crisp high-contrast light daylight interface.
Vouchers & Sales Packages
Package
Site
Group
Price
Duration
Action
Data Rollover History
ID
Old Voucher
New Voucher
Minutes Added
Data Added
Date
Buy Menus
Title
Site
Keyword
Action
VIP Groups
Group
Name
Phone
MAC
Action
Web addresses & callbacks
Found automatically. Each site only sees the links that belong to it.
Paystack Settings
Multi-Site Profiles & Admin-Set 12-Char Passwords
Approved Features for This Site
Name
Location
Site ID
12-Char Login Password
Approved Features
Status
Action
Site Feature Approval Matrix (Live Toggle per Site)
Every system feature (and any new feature added in future updates) appears below. Tick a box to activate that feature on the selected site.
Site Workspace
Features Approved to Show on This Site Page
Quick Issue Voucher for This Site
Packages & Vouchers Assigned to This Site
Package
Price
Duration
Data
Code
Package
Remaining
Status
OC200 Network Status
Click "Check OC200 Status Now" to test connection.
Omada Controller Settings
Remote OC200 Phone Connector
Per-site isolated
Pair one Android phone with one site. The phone reads its local OC200 and sends telemetry over your private Tailscale connection. No SSH or subnet-wide access is required; identical LAN ranges are supported.
Pair a phone to generate its one-time site token.
The pairing token is shown once. Copy it into the phone's config.json. The Android Termux setup is included in the installation ZIP.
Live OC200 Network Snapshot
No remote phone connector data received yet.
Live controller data has not been refreshed yet.
Omada Scan
Voucher groups
Group
Unused
In use
Expired
Linked Package
Action
Network Discovery
Tailscale
Host SSH forwarding requires the ZimaOS SSH service to be enabled and reachable from Docker. Connect with ssh -p 2222 USER@TAILSCALE-HOST. This is private to your tailnet, not public Funnel access.
Tailscale uses outbound connections and DERP relay fallback, so Starlink CGNAT or blocked inbound ports do not require port forwarding. SSH access is governed by your Tailscale ACL/grants. Funnel is public internet access; enable it only if required.
Public Funnel and private Serve are mutually exclusive on HTTPS 443. When Funnel is enabled, Center Manager configures Funnel directly (not Serve first) and checks the Funnel status before reporting public access. Enable the Funnel node attribute in Tailscale Access controls, and make sure MagicDNS and HTTPS certificates are enabled. Anyone with the public URL can reach the Hub sign-in page, so keep strong admin credentials.
Cloudflare Tunnel
Named mode: in Cloudflare Zero Trust create a tunnel, add a public hostname pointing to http://center-manager:3080, copy the token here and type that hostname below.
Auto Setup
Payment Reconciliation & Test Mode
0
Orders
0
Paid / no voucher
0
Unresolved
Reference
Method
Amount
Status
Action
Backup & Restore
Automatic encrypted backups: 7 daily + 4 weekly. The encryption key is stored in the persistent state folder. Include that folder in a secure off-device backup; without its key, encrypted backups cannot be restored.
Loading system health…
Accepts a backup file you downloaded earlier (encrypted .json.enc made with this system's key, or a readable .json copy). It is checked and added to the list below; nothing changes until you press Restore.
Works with an OmadaPay-NG backup or a Center Manager backup. Settings are never copied and nothing is deleted. Preview shows the counts first; copying makes a safety backup before it changes anything.
Backup File
Created (UTC)
Size
Action
Admin & Security — Password Manager
Encrypted Site Password Vault
Type a different password for each site (minimum 12 characters). Passwords are encrypted on the server and are not shown in ordinary site listings. Back up the persistent state folder: it contains the vault encryption key.
Site
Username (optional)
Your password
Actions
Old 12-Character Site Passwords (turned off - use Users & PINs)
Site Name
Omada Site ID
12-Char Page Password
Actions
Add user
Users
Create a new site
Docker control is not available. Reinstall with the latest compose file (it includes the docker.sock line).
Shared app update
Sites run the same app code but keep their own data, port, users and WhatsApp number. Only you (Admin) update the code: install the patch under Software Updates, then restart the sites on it. This also happens by itself when the Hub restarts after an update.