Staff permissions billing software gives a broadband shop owner separate logins, controlled screens and a record of what each person did. This guide shows how to set it up for daily recharges, plan changes and cash-counter checks without making every cashier an administrator.
What you need before you start
You do not need a technical background. Keep these items ready:
- The owner login for your billing panel.
- The names of the staff members who will use it. Give every person their own login.
- A simple list of each person’s work: customer search, recharge entry, payment entry, plan change, KYC view, stock view or reporting.
- Ten minutes to check the access and one normal counter action from each staff login.
If your shop resells more than one ISP, first understand the advantage of keeping the customer work in one panel. This guide on running OneBroadband and GTPL together gives that wider operating context. You can also read the practical guide to ISP billing software in India before mapping your team.
The shared-password problem
Many small shops start with one owner login. The owner gives the password to the counter person, then to a second staff member during leave. It feels quick, but the record can only show the shared account. It cannot tell you which person changed a plan, entered a payment or opened a customer record.
That makes ordinary mistakes harder to correct. A customer says the wrong plan was selected, a recharge is not visible at the expected time, or the day’s cash does not match the payment entries. The first question becomes “who used the password?” instead of “what happened at 4:15 pm, and which account did it?”
The safer operating pattern is simple: one person, one login, only the screens needed for that job. This is the same least-privilege approach recommended in the FCC Small Business Cyber Planning Guide. It is also why an application audit log matters: OWASP’s logging guidance describes logs as a way to reconstruct activity and investigate security or operational events.
What each staff role really needs
Start with the work, not the employee’s seniority. A trusted cashier may need to enter recharges every day but not see staff settings or the full partner wallet. A manager may need to review activity, while the owner keeps control of access changes.
Use a small access matrix like this before you create accounts:
| Shop duty | Usually needed | Keep with the owner or manager |
|---|---|---|
| Customer help desk | Search customers, view connection and expiry details | Staff access and system settings |
| Recharge counter | Customer lookup, recharge entry, payment history | ISP credentials, staff administration |
| Plan or connection desk | Customer and plan screens, connection updates | Broad reporting and access changes |
| KYC or documentation work | KYC screen and the records needed for verification | Unrelated wallet or staff controls |
| Stock handover | Stock and customer-installation screens | Full billing and user administration |
| Supervisor | Operational screens and activity review | Owner-only changes unless genuinely required |
Treat this as a starting point. Your shop may combine two duties in one person. The important part is to decide which screen is required for the task and which screen is not.
Step 1: Map each role to shop screens
Why: A permission list is easier to review when it is tied to a real counter task.
Write each role on paper or in a spreadsheet. For every role, answer three questions:
- Which screens must this person open to finish a normal customer request?
- Which actions may they perform there: view, add, update or approve?
- Which screens contain information they do not need for that shift?
For example, a recharge operator may need to find a customer, check the plan and submit a recharge. That does not automatically mean the person needs staff management, ISP account settings, partner pricing or the complete wallet view.
Success looks like: you can explain every permission in one short sentence, such as “This login can enter a customer recharge but cannot change staff access.”
Step 2: Create one named login per person
Why: A shared account removes the identity from the audit trail.
In the admin area, open the staff or team settings and add each person separately. Use a name that the owner will recognise at the counter. Do not create accounts called “counter”, “office” or “staff1” when several people may use them.
Give the staff member their own sign-in details and explain that the account is personal. If someone changes shifts, the account remains associated with that person. If a team member leaves, review and remove that person’s access as part of your shop handover process.
Do not pass the owner login around for convenience. Do not give a cashier your upstream ISP password either. In ISP Square, ISP passwords are stored encrypted and are not shown again, so staff can work through the panel without needing to know those credentials.
Success looks like: every person who handles customer or payment work has a distinct login, and the owner can identify the account from the name alone.
Step 3: Give access screen by screen
Why: Screen-level permissions keep a routine counter job focused and reduce accidental access to unrelated information.
Open each staff profile and select only the screens that match the role matrix. Start with the smallest useful set. A recharge operator might receive customer, connection and recharge access. A stock person might receive stock and installation records. A supervisor might receive the operational screens plus the audit log.
Check the difference between seeing a screen and changing information on it. If the software offers separate view and action controls, use view-only access for staff who only need to check an account. Keep changes to staff permissions, system settings and ISP connections with the owner or a nominated manager.
Your customer records may include connection details, payment history and KYC documents. Give those screens only to staff whose work requires them, and tell the team not to open a record without a business reason. Access control is an operating rule as well as a software setting.
Success looks like: a cashier sees the work needed for a recharge, does not see owner settings, and cannot use another person’s account to perform the same task.
Step 4: Read an audit log after a shift
Why: A log is useful only when the owner checks it against real shop work.
An audit log should help you answer four questions:
- Who used the system?
- What action did that account take?
- When did it happen?
- Which customer, connection or record was involved, where the panel provides that reference?
Start with the day’s unusual items: a customer who says the wrong plan was selected, a payment that needs checking, a stock handover with a missing entry or a recharge whose result needs confirmation. Note the approximate time from the receipt, UPI message or customer call. Then locate the related activity and compare it with what the staff member says happened.
Do not treat the log as a reason to accuse someone. Use it to make the next action clear. You may find a genuine selection mistake, a pending workflow that needs checking or an action that was done correctly but reported to the customer late.
Success looks like: the owner can trace a normal test action to one named account and a time, without asking every staff member for the shared password.
Step 5: Use the log in three counter scenarios
Why: Real examples turn an audit log from a security feature into a daily shop habit.
A late or uncertain recharge
A customer pays and says the recharge has not appeared. First confirm the customer, plan and payment reference. Then check the relevant account activity and the wallet ledger before taking another action.
If the first attempt timed out, do not blindly submit the recharge again. Confirm the final state in the panel and follow the normal support or reconciliation process. ISP Square is designed around this rule so a timed-out recharge is not automatically repeated without checking its outcome.
The audit record gives you a starting point: the staff login and time of the attempted action. It does not replace checking the recharge result or speaking clearly with the customer.
A wrong plan was selected
A customer says the plan entered at the counter is not the plan they requested. Use the customer and connection details to locate the event, then read the log for the account and time associated with the plan action.
If the entry was a normal staff mistake, correct it using your shop’s process and tell the customer what was changed. If the owner made the change, the log should show that too. The value is not in hiding the error; it is in making the correction accountable.
The cash total does not match
At closing time, compare the payment entries with the cash and UPI records for the shift. For an item that does not match, use the approximate time and customer reference to find the associated activity.
The log can show which named account entered the payment action. The owner can then ask one person about one transaction instead of questioning the whole counter team. Keep the ledger and the audit trail together when reviewing a correction; do not edit a record just to make the total look right.
Staff logins in ISP Square
ISP Square is built for local operators who may manage customers, recharges, partners and more than one ISP connection from one panel. Its staff logins are scoped to screens, and every action is logged against the account that performed it.
That is useful when the shop has a mix of duties. The owner can keep control of sensitive settings, let a cashier handle daily customer work and let a supervisor review activity. The same panel also keeps one customer list across connected ISPs, with connection, plan, expiry, payment and history information, so the team does not need to move between separate partner portals for every question.
If your operation includes partners or sub-partners, keep their work separate from staff access. Partners have their own login, wallet and customer responsibilities in the three-level operator, partner and sub-partner structure. A staff account is for your team; it should not be used as a substitute for a partner account.
See the trust and operating controls on ISP Square, then check current pricing before choosing a plan. Plans and purchase options can change, so use the live page for the current position.
Verify the setup before using it for a full day
Run this short check with the owner present:
- Sign in as the cashier and confirm that the expected customer and recharge screens are visible.
- Confirm that owner-only settings and staff administration are not available to that account.
- Complete one ordinary customer lookup or another low-risk test action.
- Sign in as the owner and find that action in the audit log.
- Repeat the check for the supervisor or stock login.
- Write down who reviews the log and when. A daily closing check is usually easier to maintain than a review only after a dispute.
If the action cannot be traced, stop and fix the account setup before relying on the record for a cash or customer dispute.
Troubleshooting staff access
A staff member can see too much: return to the role matrix and remove screens that are not needed for the job. Do not solve this by sharing a different password; update the named account.
A staff member cannot finish a normal task: identify the exact screen or action that is missing. Add only that permission, then repeat the test and record the change for the owner.
The log shows an action but the team cannot explain it: note the time, account and customer reference. Check the payment or recharge result first, then ask the account holder about that specific event.
Several people are still using one login: create a named account for each person and stop using the shared account. An audit log cannot reliably separate actions that all carry the same identity.
A recharge times out: do not submit a blind retry. Check the final recharge state and wallet ledger, then use the documented support or reconciliation path.
FAQ
What is staff permissions billing software?
It is billing software that lets an owner give different staff members different access, instead of using one administrator account for everyone. The useful combination is a named login, screen-level permissions and an activity record for actions taken in the panel.
Why should a broadband shop avoid one shared login?
A shared login cannot tell you which person performed a recharge, payment entry or plan action. Individual accounts make the activity attributable and make it easier to correct a mistake without blaming the entire team.
What should an audit log show?
At minimum, it should help you identify who performed an action, what happened and when it happened. Where appropriate, the record should also point to the customer, connection or other affected record; avoid putting passwords or unnecessary sensitive data into logs, as OWASP explains in its logging guidance.
Can a cashier see the ISP password in ISP Square?
No. ISP Square stores ISP passwords encrypted and does not show them again. Give the cashier only the panel screens needed for the counter task.
Does this work if I resell more than one ISP?
ISP Square connects ISP partner accounts, including OneBroadband and GTPL, and gives the operator one customer list across connected ISPs. If you resell another ISP, tell the ISP Square team which ISP you use so they can confirm the fit.
