Global Configurations
The Configuration Settings module allows administrators to centrally manage and customize the overall behavior of the ISP CRM system.
Global Configuration offers branding elements like logo and favicon to customize and whitelabel their system according to the ISP company logo and favicon.
The favicon and logo in the global configuration change the look of the superadmin login account visuals.
Also, Global Configuration offers session handling and cache management. These functionalities are provided for smooth and optimized platform performance.
Cache Management
The Global Settings page exposes buttons to flush specific groups of cached data. Caching speeds up the app by storing frequently-used lookups in memory instead of hitting the database on every request
Most caches self-clear automatically when you edit the related data (e.g., editing a plan clears the Package cache), so these buttons are mainly for troubleshooting when you suspect the UI is showing something out-of-date.
Cache Types
| Button | What it stores | Clear it when… |
|---|---|---|
| All Cache | Compiled Laravel config, routes, views, and every tagged cache below | You just deployed code/config changes, or you're unsure which cache is stale and want a full reset |
| Package Cache | Tariff plan data — speeds, actions (upgrade/downgrade/pause), data allocations used during RADIUS authentication | After editing plans, plan actions, or data allocations, customers get the wrong speed/policy |
| Location Cache | Geographic / area hierarchy | After restructuring locations |
| Router Cache | NAS/router list — IPs, RADIUS secrets, partner ownership | After adding/editing routers, NAS types, or changing which partner owns a router |
| Router Location Cache | The tree of locations served by each router | After reassigning routers to different locations |
| Currency Cache | Branch currency symbols/codes (24 hr TTL) | After changing a branch's currency, invoices/finance pages show the wrong symbol |
| User Cache | Basic user lookups | After bulk user imports/edits |
| Settings Cache | System-level settings (24 hr TTL) | After changing system defaults |
| Data Quota Cache | Per-customer remaining quota calculated from accounting logs (30 min TTL — shortest) | After manually adjusting accounting records, you need quotas to recalculate immediately |
| Enabled Languages Cache | Languages turned on for the branch (24 hr TTL) | After enabling/disabling a branch language and the language dropdown is wrong |
| User Permissions Cache | Role-based permissions for staff/partners | After changing a role's permissions and users still see old access rights |
| Branch Settings Cache | Per-branch config_settings rows (24 hr TTL) | After editing a branch configuration that isn't taking effect |
| Placeholder Cache | Translated UI strings/labels (24 hr TTL) | After updating any translation/placeholder text |
Rule of thumb: Try the single-targeted cache first. Only fall back to All Cache if that doesn't resolve it.
Clear Stale Sessions (toggle)
This is a RADIUS accounting toggle, not a web/login session cleaner.
What the toggle does
When enabled, a scheduled job runs in the background:
-
Loops through every router that has an interim_interval configured.
-
Finds users with stale sessions on that router.
-
Queues a Packet of Disconnect (POD) in the queue_coa table for each one.
-
The POD is sent to the NAS, which officially closes the session and writes a proper stop record.
When disabled, stale sessions remain in the accounting table indefinitely, and customers may appear "online" on dashboards when they aren't.
When to enable
You have routers that occasionally lose contact with the CRM. Dashboards / online-user counts are drifting higher than reality. Data-quota calculations look wrong because never-closed sessions keep accumulating time.
When to be cautious
If an interim_interval is misconfigured (too low) on any router, healthy sessions could be disconnected. Verify each router's interim interval is realistic (typically 5–15 minutes) before enabling.
