Skip to main content
System Users are the administrators and support agents who sign into your Centipid dashboard. Only primary admins can access this page. From here you can invite teammates, reset their passwords, issue API tokens, and decide what areas of the app they can touch.

​
Open the page

  1. Click the gear icon → System Settings → System Users, or use the avatar menu → System users (visible to admins only).
  2. The page loads with tabs for All Users, Administrators, and Technical Support so you can focus on a subset of staff.
  3. The table shows each user’s username, phone, email, role, internet profile (if any), and last login time.
System Users table overview

​
Create a new staff account

  1. Press Create User.
  2. Fill in the person’s first and last name, username (letters/numbers only), phone, and email.
  3. Select the Role (Admin or Support). Admins automatically receive every permission; support users rely on the custom permissions you pick later.
  4. Set a strong password (Centipid enforces 12+ characters with mixed case, numbers, and symbols).
  5. Optionally tick Send email with password reset link—Centipid will email them a reset link plus a welcome message.
  6. Choose which packages (profiles) they are allowed to see, if applicable. The Internet Profile dropdown is more than a label—it ties the staff account to a specific bandwidth profile so that when they connect through PPPoE or Hotspot (for testing or field work) Centipid enforces the same speed ceilings you set for that profile.
  7. Scroll to Permissions (details below) and tick only the modules the user needs.
  8. Save. Centipid stores the user, emails them (if requested), and logs the action for auditing.

​
Editing and actions

  • View user – open the profile to review login history, API tokens, and activity widgets.
  • Edit Permissions – update the checkbox list at any time. Admins cannot have their permissions edited (they always have full access).
  • Change password – either force a password update for someone else or change your own (admins must enter the current password when changing their own). Centipid emails the affected user when a password changes.
  • API Tokens – staff can generate, regenerate, or revoke their API tokens directly from the actions menu. Tokens show once; copy them immediately.
  • Delete – remove a system user (cannot delete yourself).
Centipid includes safety rails such as rate limiting OTP emails, validating new email domains, and caching permission selections so edits remain responsive.

​
Permission groups

Think of permissions as plain-English switches for each area of the app. When you edit a system user you’ll see sections such as Users, Payments, or Vouchers with simple checkboxes:
  • View list – lets them open the table/list for that feature.
  • View details – lets them open a single record.
  • Create – allows new records.
  • Edit – allows changes to existing records.
  • Delete – removes records (only shown when it’s safe to delete that type of data).
Whenever you grant Create, Edit, or Delete, Centipid automatically checks the “View list” box so staff can actually see what they are working on. Some modules (for example Payments) purposely hide Delete, because those records must stay on file.
FeatureWhat it controlsTypical access
Active UsersLive session list plus disconnect buttons.Support teams (view only).
CampaignsMarketing campaigns that display on captive portals.Marketing or admins.
EmailsMass email log and templates.Marketing or admins.
EquipmentInventory of routers / radios you’ve loaned out.Field ops, warehouse, admins.
ExpensesFinance → Expenses ledger.Finance team.
InvoicesFinance → Invoices page (create, mark as paid, download).Finance/support.
LeadsProspect tracker and “convert to client” button.Sales/support.
MikroTik (NAS)Router list, diagnostics, remote Winbox tools.Network engineers.
PackagesPackage definitions and quick templates.Product/finance leads.
PaymentsPayment table (record cash/bank receipts).Finance/support (view + create).
ReferralsReferral partners dashboard.Business development.
Expiry Dates (Schedulers)Manual expiry timers/grace periods.Support/billing.
SMSSMS gateway, templates, and log.Comms/marketing.
TicketsSupport ticket queue.Support team.
UsersSubscriber management (profiles, packages, credentials).Support/admins.
VouchersVoucher batches, exports, printing.Retail/support.
Assign only what each teammate needs—support agents typically get users, tickets, payments, and active_users, while finance might only need payments, invoices, expenses, and packages.

​
Tips

  • Use descriptive usernames (e.g., nairobi-support-1) so audit logs are easy to read.
  • Revoke API tokens whenever a staff member leaves, then delete their system account to remove dashboard access entirely.
  • Schedule a monthly audit: export the System Users table, verify that each person still works with you, and prune unused accounts.
  • Combine permissions with the Audit Logs (Administration group) to see exactly who changed which records.

​
Captive portal access

System Users can also authenticate on any Centipid captive portal with the same username + password they use for the dashboard. This is helpful when field engineers need to test Wi‑Fi splash pages or PPPoE dialers from the customer side. Their browsing session will obey the Internet Profile you assigned, so give engineers a high-speed profile and limit other staff to standard speeds if you need to protect capacity.