How easy was NetPulse for your work this week?
Nothing waits for you
Your pages
The network right now: traffic, boards, radius states and what needs attention today. Every number opens its page.
Whole network
Network traffic · last hour
Download
Collecting data from the boards…
Upload
ProRadius
Customers by owner
Biggest resellers
Customers · active in ProRadius · online on the boards nowBilling and money
Consumption levels
Clients by VLAN
Click a VLAN to see its clients| Board | VLAN | Online | Full | Middle | Normal |
|---|
Router boards
| Board | Host | API | Online clients | Now ↓ (real · CDN) | Now ↑ | Today ↓ / ↑ | Last poll |
|---|
Everyone connected now, with their speed, board, VLAN and usage. Click a customer for their page; filter by board or state.
| Username | Consumption | Real ↓ / limit | Real ↑ / limit | Full today | IP | Board | VLAN | Uptime |
|---|
The radius as it is: every user, their profile, state and expiry. Read live; changes are made from the customer's page.
Profiles & speed limits
| Profile | Billing price | Users | Online now | Speed limit on the boards (↓ / ↑) |
|---|
ProRadius users
This billing month in figures: billed, collected, owing, by region and collector. Click a figure to see its list.
Collection rate
Share of each month's bills that has been paid
Cash received per month
All receipts dated that month, whatever bill they paid
Customers billed and paid
Days of collection
Payments by day of the month, over the chosen months
Payments by weekday
Over the chosen months
Owed now, by region
Active customers
Cash by collector and month
Receipts in Billing, darker = more cash
Profiles this month
Active customers billed per profile, and what they bring in
Resellers, collectors and customers
Reseller credit by month ($)
Credit you transferred to resellers in ProRadius, what they used it on, and what they paid you
What each reseller owes you
In dollars, since each reseller's opening date
Still with collectors
Collected in NetPulse, not yet handed to the office
Every bill of the chosen month: who paid, who owes, and the collector. Search by name, username, phone or address; filter and sort each column.
Stopped in the radius, still billed
Stopped by hand in the radius panel, not through NetPulse: Billing still bills them. Deactivate them in Billing too (this month's bill as you choose), or keep them active and say why.
| Customer | Seen since | Kept active |
|---|
Bills to approve
Worked out by NetPulse (a customer activated again: the rest of the month). Nothing is in Billing until you approve it, as it is or with another amount, or decide there is no bill.
| Customer | Why | Amount | By |
|---|
| Customer | Status | Remaining | Paid | Price | Old balance | Profile | Address | Last payment | Collector | Received by |
|---|
Every customer in Billing: what they owe now, their profile and price, address and collector. Click one for their page; stopped and free customers are in the list filter.
| Customer | Owes now | On the boards | Phone | Profile | Monthly price | Address | Collector |
|---|
What each collector holds and handed over, their payments of the month, and their statement. The accountant receives cash here.
Cash collectors took through NetPulse, what they have handed to the office, and what is still with them.
| Collector | Still with them | Collected | Handed over | Today | Last handover | Their customers owe |
|---|
What this collector holds, customer by customer
| Date | Customer | For | Amount |
|---|
The accountant keeps the cash book: what she takes is in it at once, shown here as handed over. Nothing to hand over to herself.
Handovers
| Date | Amount | Note | Received by |
|---|
Payments collected
| Date | Customer | Month | Amount |
|---|
WhatsApp reminders
What the collector app writes when a collector sends a customer a reminder: the 1st and 2nd time this month the polite message, from the 3rd the strict one (he then shows on My work, to stop or keep). {name}, {month}, {amount}, {company} and {phone} are filled in for each customer.
The resellers: their users in the radius, what they owe us, and payments received from them.
| Reseller | Owes you | Credit in ProRadius | Customers | Credit given this month | Used this month | Paid this month | Last payment |
|---|
Traffic
Live · last hour ·
Download
Collecting data from the boards…
Upload
Download (upload under it), from the boards' counters: ours, each reseller alone, and all resellers together. Tap a row for its days.
| Who | Now | Today | Yesterday | 7 days | 30 days |
|---|
Opening balance and details
Statement
| Date | Entry | Amount | Owed after | Note |
|---|
By month
| Month | Credit given | Used | Used on |
|---|
Customers
| Customer | Phone | Profile | Status | Expires |
|---|
Each month: close the month that ended (whatever is unpaid is carried into the customer's balance), then create the new month (one invoice per active customer, on their pay day, with their balance brought forward). Every step shows what it will do before anything is written.
Close a month
Closes every open invoice of the month. What a customer has not paid is added to their balance and shows on their next invoice.
Create a month
One invoice for each active customer whose profile exists: their own price if set, otherwise the profile's, dated on their pay day.
Recent months
| Month | Invoices | Open | Billed | Still open |
|---|
Customers come from the radius: every new user under your account that is not in Billing appears here. Check the details, choose the profile, pay day, first month and collector, then confirm. While the staff still use the old billing system, also enter the customer there; it moves to Done by itself once it reaches Billing.
| Customer | Radius | Decision | Billing |
|---|
When a customer calls: find them, open their page to check the live status and run diagnostics, then log the call there. Solved on the phone, or open a visit.
Calling again and again
| Date | Customer | About | Outcome | Ticket | Note | What NetPulse showed | By |
|---|
Work for clients who are not subscribers (cameras, cabling, a building's fiber...). Each client once, with their tickets, what they owe and their payments. Their tickets open from here or from Tickets with an outside topic.
| Name | Phone | Address | Tickets | Owes | Last work |
|---|
Tickets
| # | Topic | Status | Date | Total | On account |
|---|
Payments
| Date | Amount | How | Taken by |
|---|
Every ticket: new, assigned, on site, waiting, closed. Open a ticket to see its thread, charges and messages to the technician; filter each column.
| # | Customer | Topic | Priority | Status | Technician | Updated |
|---|
The technicians' load today and the cash each holds; ticket topics, the price list and the visit fee.
Technicians
Ticket topics
| Name | Department | For | Visit fee | Own fee | Active |
|---|
Visit fee
Charged once when the technician arrives, on topics marked with a visit fee. Set by the admin and the accountant.
Price list
Services and materials the technicians charge. Materials go to the stock-sales pot, services to the visit-fees pot.
| Name | Kind | Price | Currency | Sold by | In stock | Cost | Cost in | Active |
|---|
Where every item is: the office, each technician, stations and buildings, and items lent or on trial at customers. Items charged on a ticket come off the technician by themselves.
Asked by technicians
Hand-outs not received
Between technicians
Items a technician gave a colleague that were refused, or not accepted within a day. They are in neither box until you decide.
On their way (waiting for the colleague to accept)
Damaged or lost: to approve
Faulty and at repair
Faulty items brought by technicians, from their box or from a customer. Send them to repair, back to the supplier, or write them off; repaired ones come back into the office's stock.
Cable leftovers
What is left of a technician's older boxes once he has a newer one. Untouched for 14 days, it is marked: write it off, or leave it while it is still useful.
| Technician | Piece | Metres left | Last used |
|---|
Stock counts
On the count day every technician holding stock counts their box in the phone page, without seeing what NetPulse expects. Each difference comes here: found is added; missing is charged to the technician (from the salary or in cash) or waived with why. The office is counted once a month; from November a month closes only after its office count.
Last counts:
Low in the office: suggested purchase
Back to the minimum, plus what was used in the last 30 days; cable in whole boxes. The estimate is at the average cost.
| Item | In the office | Minimum | Used (30 days) | To buy | Estimate |
|---|
Stock on hand
| Item | Office | With staff | Stations | At customers | Total | Minimum | Value at cost |
|---|
| Place | Item | Quantity | Rolls |
|---|
Record a movement
Count
Enter what you counted; the difference is recorded as found or missing. For cable, count each roll (or leave the roll empty to add a new one).
At customers
Trials past their day and customers stopped in Billing come first: collect the item, or charge it if the customer keeps it.
| Customer | Item | Quantity | What happened | Since | Trial ends |
|---|
Stations and buildings
| Name | Kind | Address | Active |
|---|
| Item | Quantity | Rolls |
|---|
Replace equipment
| Date | What happened | Item | Quantity | From | To | By | Note |
|---|
Into the network
Equipment and cable installed free at stations and buildings in the month, less what came back out, at cost.
| Item | Installed | Came out | Net | Cost |
|---|
Movements
| Date | What happened | Item | Quantity | From | To | By | Note |
|---|
Equipment sold
| Date | Customer | Item | Quantity | Amount | Paid | Sold by | Ticket |
|---|
Reports
Stock each technician holds (at cost)
Used per technician (sold, installed, lent)
Used per ticket type
Shrinkage: missing at counts and written off
| Technician | Missing (cost) | Charged | Waived (cost) | Written off (cost) |
|---|
Bought outside
| Technician | Times | Sold for | Profit handed in |
|---|
Salvaged parts
Items and categories
| Item | Category | Unit | Price | Cost | Minimum | Pack |
|---|
Money paid out of the cash a technician holds: cable, small parts, roof rent, fuel, a refund, a supplier. It waits for the accountant; once approved it comes off the technician's box and goes into the cash book as an expense.
My box
| Visit fees | Stock sales | Subscriptions |
|---|
Record spending
Waiting for approval
| Date | Technician | What for | Amount | Taken from |
|---|
Spending
| Date | Technician | What for | Amount | Status |
|---|
A supplier's invoice with its full amount: items received into stock (how many only; the total is shared over them as their cost) or outside labor for stations and fiber. Paid now from the cash book, or later (the supplier is owed it). Keep a photo of the paper invoice.
Record an invoice
Invoices
| Date | Supplier / worker | What | Amount | Paid | Photo | Recorded by |
|---|
What each provider's plans cost you and what you sell them at, your balance with each provider, and everything he charged: renewals, new customers, added days and plan changes. Read from each provider's radius with your own login there; nothing is typed.
What the provider charged
Each reseller on this radius: what his customers' renewals and changes took from his balance in the period, what was put on it, and what is left. His customers are his own: they are not listed here.
| Reseller | Charges | Charged | Topped up | Balance left |
|---|
| Customer | Plan | Charges | Costs you | Margin |
|---|
| Date | What | Customer | Plan | Costs you | You sell at | Margin | Balance after |
|---|
What each bandwidth provider charges for a month, and every part paid against it: by the accountant from the cash book, or by the admin from his own money. Each bill shows who paid what and what is still owed.
Bills
| Month | Provider | Bill | Paid by the accountant | Paid by the admin | Left | Status |
|---|
What the company owes each supplier: purchases on credit, minus payments from the cash book or from a technician's box.
Suppliers
| Name | Phone | Owed | Last entry |
|---|
| Date | Entry | Amount | Note | By |
|---|
Each technician's month: tickets, visits, time to arrive and on site, the problems fixed, fees and materials charged, fees lowered, bills collected, days worked, late starts, overtime and leave. Before the month's billing closes.
Customers, growth, churn, retention and revenue, month by month, for planning. Every figure says how it is worked out (ⓘ). Months marked * are month to date; † the war in the south (2026-03 → 2026-06, displaced).
Last 12 months
New, stopped and reactivated
Active customers
MRR and cash (USD)
| Month | Active | New | Stopped | Reactivated | Net | Growth | Churn | MRR | ARPU | Cash | Source |
|---|
Retention by starting month
Customers first billed in a month, and the share still billed 1, 3 and 6 months later (… : not come yet). 2023-04, the first month billed, starts no cohort.
| Started | Customers | After 1 month | After 3 months | After 6 months |
|---|
Breakdown
· Region and collector as they are now (Billing keeps no history of them); a plan is the bill's.
Top by customers
Top by cash revenue
| Group | Active | Month before | Net | New | Stopped | Churn | MRR | ARPU | Cash |
|---|
Who stopped, and why
Reasons
| Stopped | Customer | Plan | Region | Collector | Reason | Stopped by | Now |
|---|
Compare two months
| KPI | A | B | Difference | Change |
|---|
Risk and opportunity
Expiring in 30 days
| Username | Name | Plan | Expires | State |
|---|
Active, no use for 30+ days
| Username | Name | Plan | Region | Collector | Last online |
|---|
Plans with rising churn
Customers who keep needing us: tickets, visits and calls over the period, the same problem coming back (not really fixed), and what they were charged. Click a customer for their page.
| Customer | Tickets | Visits | Calls | Same problem again | Problems | Charged | Last |
|---|
Each technician's working hours. At the start time the technician confirms they started (reminded every 15 minutes for an hour, then you are told); you are told when they are on the ground. Breaks, leaves, overtime (only with tickets worked in it) and tickets closed out of hours wait for your approval here.
Today
| Staff member | Now | Hours | Started | Ended |
|---|
Waiting for your approval
Weekly hours
The hours each weekday, every week. Leave a day empty for a day off. A night shift ends after midnight (e.g. 20:00–02:00).
Change one day
| Date | Staff member | Hours | Note |
|---|
Leaves and days off
| Dates | Staff member | Kind | Note |
|---|
Messages about your tickets: new tickets, notes written on tickets you work on or opened, installation details that were changed. The sender sees when each one reached you and when you opened it.
The money side of maintenance: prices that technicians changed or bought outside, items to add to customers' bills, and the cash each technician holds until they hand it to you.
Prices waiting for you
| # | Customer | Item | List price | Charged | Technician |
|---|
To add to bills
Enter each one on the customer's bill in the billing system, then mark it added.
| # | Customer | Item | Amount | Date |
|---|
Unpaid promises
Customers who promised to pay later ("bokra"). When the money comes, mark how it was paid.
| # | Customer | Item | Amount | Promised for |
|---|
Items used without a ticket
The last 60 days. Void one to put the item back in the technician's box and take its money off his.
| Date | Technician | Item | Amount | State |
|---|
Cash with technicians
| Technician | Visit fees | Stock sales | Subscriptions | Left from earlier handovers |
|---|
Received from technicians
| Date | Technician | Detail | Amount | Received by |
|---|
The office's money: cash in hand and on Whish, per pot. Every entry in and out, the day-by-day ledger, handovers to the admin, and closing a month once its figures are final.
Handovers to confirm
Money the accountant handed to you. Confirm each once you have received it.
| Date | Pot | Amount | By |
|---|
Handed to the admin, to come back
Handovers marked "to come back": the admin says what he gave back (cash or Whish), the accountant confirms she got it, and it goes back into the pot it left.
| Date | Pot | Handed | Back | Still to come back |
|---|
Entries
| Date | Kind | Pot | Handed in by | Technician | Details | LBP | USD | By |
|---|
Paid by Whish on tickets, to record
Bills paid by Whish to the office: check they arrived
Staff took these bills by Whish to the office's account. Confirm each one when you see it in the Whish account: then it counts in the cash book.
Ledger: day by day
What was held at the start of each day, what came in, what went out, and what was held at its end: cash in hand and on Whish, per currency, all pots together. Closing a month stops any change in it.
The month per pot
Pots
Pots of your own beside maintenance, equipment and subscriptions, for money you record by hand (money in or out). Hide one you no longer use: its money and history stay.
Categories
Collectors are paid for every bill they collect (any kind of bill), at their own amount per bill. Bills are counted from Billing for the month; paying records an expense in the cash book.
| Collector | Bills collected | Amount per bill | Other expenses | Due | Paid | Left |
|---|
New installations sent by the technicians from the app. Check each one, fill what is missing and confirm the username; then "Send to radius" opens ProRadius's Add user page (logged in as your own account) with everything filled: check it there and submit. When the user appears in the radius, the new customer is confirmed with these details and the ticket is closed.
| Date | Technician | Customer | Profile | Money taken | Status |
|---|
Customers active only until a date, and plan changes charged by days. When a period ends, stop the user in the radius (the arrow opens their page there); it leaves this list by itself once the radius shows them stopped. While the staff still use the old billing system, the accountant also enters each one there and ticks it here.
Stopped mid-month: charge by days
Customers stopped in Billing with a bill for this month or the last. The last day worked comes from the radius (its expiry date); change it if needed. Charging corrects the bill (kept in the bill's history with the reason).
| Customer | Month | Full price | Last day worked | By days |
|---|
What is missing or wrong in Billing's data, customer by customer. Nothing is changed here: fix each one in the billing system; it leaves this list at the next check.
| Customer | Status | Region | Details |
|---|
Each region with its sub-regions, once each and without numbers. Billing's own sub-regions (numbered, duplicated, misspelled over the years) each point to one of these; Billing itself is not changed. New customers are given a sub-region from this list.
| Sub-region | Customers | Names in Billing |
|---|
Billing customers who are no longer live in the radius, checked against ProRadius's archive of deleted users (kept in NetPulse's database), and your own archived users who never were in Billing. Nothing is changed on either side.
| Customer | Billing | Owes | Radius archive |
|---|
Debts the accountant wrote off (customers who left and will never pay), month by month, with why. Undo puts the debt back.
| Date | Customer | Amount | Why | By |
|---|
The parallel run's check: the old system and NetPulse Billing compared row by row — customers, this and last month's bills and every open one, the last 45 days' payments, the lookups, and each day's payment totals. Kept every evening; at month end it shows the two agreed.
| Row | What differs | Old system | Billing |
|---|
Payments per day, both sides
| Date | Old: payments | Old: LBP | Old: USD | Billing: payments | Billing: LBP | Billing: USD |
|---|
Kept results
| Date | Kept at | Written to | Differences | Days that differ |
|---|
Your own customers in Billing compared with your own users in the radius (your reseller account in ProRadius). Nothing is changed on either side: fix each mismatch where it belongs.
| Customer | Problem | Billing | Radius |
|---|
What this NetPulse needs before its first working day, and what can follow. Each step is checked against what is really there, so it stays true whichever page did the work.
The dollar rate
How many pounds one dollar is. Bills and payments in the other currency are worked out with it. A new rate applies from now; what was recorded before keeps the rate it had.
Your papers and the speed test
These are your company's own. Leave one empty to do without it; all can be changed later on Rules & names.
What customers already owe
A sheet with three columns: username, amount, currency (LBP or USD; empty means the customer's own). Each amount is added to what the customer owes, in the currency his bills are in. You see what every line would do before anything is written. A customer gets his opening balance once: bringing the same sheet again changes nothing.
Or one customer by hand
Added so far
| Date | Username | As given | On his bill | From | By |
|---|
Staff accounts: their roles, what each may do (ticked per feature), their collector link, and resetting passwords.
Users
| Username | Name | Role | Collector | Status | Last sign-in |
|---|
What each role may do
A new account starts with its role's ticks; each person can then be given more or fewer on the Users tab. The admin has everything. A number is how many of the group's permissions the role holds.
Collectors (in Billing)
The collectors customers are given. Add one here or with a new collector account; a retired collector leaves every list, and their past bills keep their name.
| Collector | Status | NetPulse account |
|---|
Resellers each role sees
Which resellers' users each role is shown (ProRadius users, the overview, the reseller page). Admins and developers see every reseller; a reseller account sees only its own. Changing users in the radius stays limited to your own reseller.
Connections that ended on the boards. A short session is usually a drop, not the customer switching off. When several users on the same VLAN lose their connection within a few minutes, NetPulse raises an alert: a possible fault on that VLAN.
Possible faults on a VLAN
| Raised | Board | VLAN | Who dropped |
|---|
Customers with short sessions, by VLAN
New addresses waiting for your approval: entered on a move ticket (by the technician or the office) or on a customer's page. Approved: written to Billing and the radius, and the customer's collector is told the address. Refused: the one who entered it is told.
| Customer | Was | New address | Entered by |
|---|
Customers who moved
This month's moves and those waiting for the address: check each one (his collector, his bill), then Done takes it off My work.
| Customer | Was | New address | Collector | State |
|---|
Type a building or a street: every customer whose address has those words, and whether they are connected now. When everyone there is down together, the problem is at that place (their AP or VLAN is named when they share one).
| Username | Name | Address | Now | VLAN | AP |
|---|
Same building: suggestions
Customers whose addresses name the same building in the same sub-region, or whose phones' points are a few metres apart.
The network as the team drew it in the Dude: each area (VLAN) with its devices and the links between them, and each device's state now. Press an area to go into it; press a device to see it and who would be affected if it went down.
The company's MikroTik devices as the Dude reads them, every 2 minutes, read only: their state, what each AP carries, and what happened to them. Whoever watches drops gets a message when a device reboots, its voltage drops, it gets too hot or a link goes down.
What happened (now, and the last 7 days)
| When | Device | What | Detail |
|---|
Devices
| Device | Model | Version | Firmware | Serial | Up for | CPU | Voltage | Temperature | Links up | Antennas | State |
|---|
Each profile's monthly price in Billing. A new price counts from the next bills: customers with their own (special) price keep theirs, and bills already made stay as they are. A price above 1,000 is billed in LBP, otherwise in the profile's currency.
| Profile | Active customers | With their own price | Price |
|---|
How this company works, as settings: the names the code looks for (ticket topics, the office collector, who the cash is handed to), its addresses, and its money and work rules. Every one starts as the code had it. A change applies from that moment, for everyone, and is kept in the audit log with its reason.
Is everything NetPulse depends on answering: the database, the billing data, the boards, the radius, the background jobs, disk space and last night's backup. Checked every minute; when something stops you get a message, and again when it is back.
Went down / came back (last 7 days)
| When | What | Detail |
|---|
Server errors (last 24 hours)
| When | Request | By | Error |
|---|
Background jobs
| Job | Every (min) | Last run | Status | Failures | Detail |
|---|
How the staff find working with NetPulse during the first two months: what they wrote (feedback from any page, and the weekly question), where they spend their time, the errors they ran into and what they searched for without finding it. Answer each point; a reply reaches its writer as a message. Note what you changed, to see whether the weekly score moves.
Weekly score (1 = very hard, 5 = very easy)
Feedback
| When | Who | Page | What they said | Status |
|---|
What slowed them down (weekly question)
| Week | Who | Score | What they said |
|---|
Errors they ran into
Every message a page showed as an error. Many times the same message often means a confusing step, not a mistake by the user.
| Error | Page | Times | People | Last |
|---|
Crashes
Unexpected errors in the phone app and in the pages, sent by themselves with where they happened in the code. Tap one to see the details.
| Error | Where | Times | People | Last |
|---|
Searched for, not found
| Searched | Times | People | Last |
|---|
Where the time goes
| Page | Role | Where | Opened | Minutes | People |
|---|
What we changed
When a dropped connection counts, and how many on one VLAN raise an alert. The admin's.
Drop alerts
When to call a session short, and when several drops on one VLAN make an alert. The alert goes to troubleshooters, technicians and admins (whoever may see Drops).
Customers whose bill was still not fully paid on the day you choose. Tick the ones to stop, say why once, and NetPulse stops them in the radius (each stop is kept with its reason). Customers already stopped or expired cannot be ticked.
Suspended for non-payment
| Customer | Phone | Suspended | Owes now | Where it stands |
|---|
Employees and their monthly salary. An advance is paid out of the cash book and stays owed; on pay day the salary less the advances not yet settled is paid in one entry, which settles them. Expenses in the cash book can say who spent them.
Employees
| Name | Monthly salary | Advances owed | Spent this month | Advances this month |
|---|
Pay day
| Name | Monthly salary | Advances taken off | To pay |
|---|
| Date | What | Description | Amount |
|---|
Which notifications reach you on this computer and phone, and the sound they make.
This computer
Notifications appear on this computer even when NetPulse is not open, as long as the browser runs.
Notify me about
What you receive is set by the admin for your role. What is about your own work (your day, your tickets, your stock) and messages from the admin always arrive.
Who is told what
Tick the topics each role receives. A person gets a topic when one of their roles has it (and their permissions let them see it), unless his notifications were chosen for him on the Users page: then only those. "·": the role cannot see that work.
Send a message to the staff
It arrives in their Messages, on their phones and desktops, whatever they turned off.
The accountant's Excel books from January to October 2026, as they were written: the cash book (money in from collectors, money out per person) and the stock book (each item's count at the start of the month and where it went). History only: the live cash book and stock are separate.
Printable reports and Excel downloads: the month's summary, the unpaid list for collectors, payments, each collector's takings, who owes by months behind, and the last months side by side.
Each board or radius server can have several device accounts. Read-only accounts are used for reading; changes go through a read/write account, and only for NetPulse users you give the permission to. Adding a server that is already here adds the account to it, so nothing is read twice.
Boards (MikroTik)
Radius servers (ProRadius)
The Dude
The Dude server runs on a MikroTik router (the one with the dude package). NetPulse signs in to that router's API with an account you give here, and only reads: its devices and their state. Nothing in the Dude is changed. A read-only account is enough.
Backups to Google Drive
Every night the server backs up the database. With a Google account connected here, NetPulse also uploads that backup to its Drive, compressed and locked with a key, and keeps the last 5 there: the oldest is deleted only after the new one is up. NetPulse sees only the files it made in that Drive, nothing else.
Google app keys (once)
- Open Google Cloud with the Google account, and make a project (any name, e.g. NetPulse): console.cloud.google.com
- APIs & Services → Library → "Google Drive API" → Enable.
- OAuth consent screen: External; app name NetPulse; your email. Then Publish app (In production), so the access does not expire after 7 days.
- Credentials → Create credentials → OAuth client ID → Web application. Under "Authorised redirect URIs" add exactly the address below.
- Copy the client ID and the client secret into the boxes here, save, then press Connect.
Redirect URI:
Everything changed in NetPulse, by whom and when: payments, corrections, radius changes, permissions.
| Time | User | Action | Target | Details | IP |
|---|
The developer's tools: the server, its jobs, the databases and their state.
Developer accounts
| Username | Name | Status | Last sign-in |
|---|
System status
Background jobs
Each job runs on one server at a time (the one holding it). Router polling is not listed: every server keeps its own.
| Job | Every | Last run | Status | Runs / failures | Held by |
|---|
Slow requests
| Request | Times | Last 24 h | Average | Slowest | Last |
|---|
Mirror into the old system
| Table | Last pass | Copied | Waiting | Problem |
|---|