শেয়ার

Administration

The admin panel (/admin, for accounts with the admin or staff role) runs the installation: customers, plans and payments, the monitoring infrastructure, the public website and the system settings. Every admin action is written to the audit log.

Overview

Dashboard shows the platform at a glance: users, organisations, monitors by status, servers, open incidents, revenue, the queue, and warnings when the cron job is late or probes are offline.

System health is the platform watching itself: when the scheduler, worker, cron and the hourly/daily housekeeping last ran (with an alarm when the cron is more than 3 minutes late), queue depth by state and queue, every probe with version and last contact, agents online/offline, database reachable and size, result and metric row counts, failed notifications in the last 24 hours, checks in the last 24 hours, storage writable, PHP version, load, free disk and memory.

Audit log lists every account change and admin action (who, what, on which object, from which IP, with details), searchable, kept for the retention period in Settings (365 days by default).

Customers

Users: search, open, edit (name, e-mail, role user/staff/admin, status active/inactive/banned, verified, timezone), reset the password, see login history and sessions, sign a user out everywhere, impersonate to see what they see, delete the account (which hands over or deletes their organisations). New users can be created by hand regardless of the registration switch.

Organisations: every organisation with owner, plan, member count and usage; change the plan or grant a subscription for N months (trial or paid), suspend, open its monitors and servers.

Monitors and Servers: platform-wide lists with owner, status and last check, with the same actions as the owner has (pause, test, delete) for support. Since 2.1.3 Edit on a monitor opens the full monitor form; it works inside that monitor's own organisation (its plan limits, groups, tags and alert channels), and a note at the top says so.

Incidents: every incident on the platform, open first.

Agencies & resellers (/admin/resellers): every organisation of type Agency or Reseller with its plan, clients used / allowed, monitors in the pool, and whether reseller billing and white label are active.

  • Reseller limits per plan: for each plan the number of Client organisations (0 none, -1 unlimited) and the Reseller billing switch. The plan's monitor, server and status-page limits become the pool shared by the agency and all its clients.
  • Make an organisation an agency: enter the Organisation id and pick Agency or Reseller. A client organisation cannot become an agency.
  • Opening an agency shows the pool usage and Reseller settings: Client organisations (blank = what the plan allows, -1 unlimited, 0 none), Reseller billing (as the plan says, On or Off) and an internal Note; the white-label state, brand name, panel domain and all-time revenue; Change type (Agency, Reseller or back to a normal team); and Clients and allocations, where you can set each client's monitor, server and status-page cap (0 = no own cap).

See Agencies and resellers.

Enterprise quotes (/admin/quotes): requests sent from the public /enterprise page, newest and open first, filterable by status (New, Contacted, Quoted, Won, Lost). A request shows the contact, company, team size, monitors, servers, needs, details and IP. Follow-up sets the status and staff-only notes and has a Write an e-mail link. Create custom plan (administrators only) makes a plan that is not shown on the pricing page and puts the chosen organisation on it at once: pick the Organisation (the requester's organisations are listed by e-mail; otherwise enter the Organisation id), the Plan name, Price per period, Billing (yearly or monthly), Months granted now (1–60), every limit (-1 = unlimited), the switches White label & custom domains, SMS & WhatsApp alerts and Reseller billing, and the Features shown to the customer. The request is marked Won and the customer is e-mailed.

Billing

Plans: edit each plan's name, slug, prices (monthly, USD, yearly), every limit (monitors, servers, interval, history days, locations, channels, members, status pages, API tokens, API rate), switches (white-label, reports, SMS, e-mail alerts, embed), trial days, features list, public/active and order. Two limits were added in 2.1: AI calls / month (AI summaries per organisation; -1 unlimited, the default, 0 not included) and Client organisations (agency) (0 by default). The reseller-billing switch of each plan is set on Agencies & resellers. The default plan for new accounts is picked in Settings.

Payments & invoices: pending manual payments with the proof uploaded by the customer; approve (grants the subscription and e-mails the customer) or reject with a note; the full invoice list with status changes and refunds; gateway references.

Coupons: percent or fixed amount, limited to plans, max uses, expiry, active/inactive.

Payment methods (/admin/gateways, rebuilt in 2.1.1): a catalogue of every method as a card, grouped into Cards & wallets (Stripe, PayPal, Paddle, Razorpay, Paystack), Bangladesh (SSLCommerz, bKash, Nagad, aamarPay, and bKash / Nagad / Rocket Send Money), Bank & manual (bank transfer, custom) and Crypto (USDT), with a status pill (enabled, disabled, sandbox), a quick on/off switch, search and filters. A method's page (/admin/gateways/<code>) holds its keys (stored encrypted), sandbox or live, a fee in % and/or a fixed amount (added to the invoice and paid by the customer), minimum and maximum amount, the charge currency with an exchange rate, display name, instructions, logo and order, the callback / webhook addresses with copy buttons, and Test credentials. A method that is on but misses required keys is not offered; a method outside its amount limits is shown greyed with the reason. For Paddle the full setup is in Plans and billing.

The API methods are confirmed on the server with the provider before an invoice is paid (SSLCommerz validation API, bKash execute/status, Nagad signed verify, aamarPay trxcheck, Razorpay signature and order, Paystack verify; webhooks are signed and replay-protected). Manual methods ask the customer for the sender number, transaction id and a proof picture; the invoice shows Pending review.

Payment proofs (/admin/payment-proofs): the queue of manual payments - approve (the invoice is paid, the plan applied and the payment-received mail sent) or reject with a reason (the customer sees it and can pay again). A transaction id already used on another invoice is refused. Payment report (/admin/payment-report): totals, counts and fees per method and month, with CSV export.

Infrastructure

Probes: the main server (core) and every remote probe with code, region, status (new, online, offline, disabled), version compared with the platform's, last contact, load and queue from the last heartbeat, spool size. Add a probe (which gives the one-time registration token), regenerate the token, mark public/private, set max jobs and weight, disable. See Probes.

New in 2.1 on Probes:

  • The list shows each probe's Network (ISP and ASN), Jobs/min (last hour), Fail 24h (share of failed checks in 24 hours), the queue waiting on the platform and on the probe, and a draining badge.
  • A probe's page adds stat cards for Jobs per minute, Failure ratio (24 h) (red when it is above 5 % and twice the platform average), Job routing (draining or takes jobs) and Network, plus a Checks per hour - 24 h chart.
  • ISP, ASN and Network name can be typed in, or filled by Look up ISP / ASN (RDAP) from the probe's IP. The RDAP service setting (default https://rdap.org/ip/) is the address asked.
  • Drain stops sending new jobs to a probe and moves its waiting checks to other locations; the probe stays registered. Stop draining lets it take jobs again.

These features need the 2.1 database update (db_update.php); until then the page asks for it.

Browser checks (/admin/browser): which Chrome or Chromium the main server uses for browser monitors. Detection shows the browser found (by the configured path or a standard install location), its version, the operating system, whether proc_open is available, the temporary folder and how many browser monitors reported a missing browser in the last day. Chrome / Chromium executable sets a fixed path (empty = detect automatically). Test now starts the browser, loads a page and shows the timings (start-up, DNS, connect, first byte, DOM ready, load, first and largest contentful paint, layout shift), requests, transferred bytes, failed and blocked requests, console errors and a screenshot. Probes find their own browser; set the AIM_CHROME_PATH environment variable on a probe whose browser lives elsewhere. See Transaction and browser monitors.

Queue & workers: the background jobs table by queue (check, notify, webhook, report, system) and state (pending, reserved, done, failed, dead), the workers seen recently, dead jobs with their last error and a retry button, and a prune action.

Agents: every server agent across organisations with version, OS, interval, last heartbeat and status, so outdated or silent agents are easy to spot.

Notification log: every delivery attempt on the platform (channel type, target, event, sent/failed/skipped, attempts, the provider's answer), filterable by organisation and status.

Website

Pages: the public pages (/p/<slug>): title (English and Bengali), body, footer placement, order, active. The installer seeds About, Terms, Privacy, Cookies, FAQ and Refund pages.

Blog & changelog: posts of type blog or changelog with slug, excerpt, body, version (for changelog entries), published flag and date. The changelog is shown at /changelog, the blog at /blog (can be switched off in Settings).

Contact messages: messages from /contact with name, e-mail, subject; reply from the panel (sent with the Contact form reply template) and mark as handled.

System

Settings is organised in tabs (staff may look, only administrators may change):

  • General: site name, URL, tagline and description; admin, contact and support e-mail; default language and timezone; currency, USD→BDT rate, yearly discount %, grace days, tax rate and label; registration open/closed, e-mail verification required, notify the admin of registrations, new-device e-mails, the default plan for new accounts, blog on/off.
  • Brand: logo (light, dark and e-mail versions; nothing uploaded = the official AllInOneMonitor logo from assets/brand, light or dark to match the theme), favicon, footer text, cookie banner, the status page linked in the footer, and Brand colours (2.1.1): the brand colour as a hex code (stock: the official emerald #059669; the short #36f also works) or with the picker, a hover / second colour (automatic = a lighter shade), the text colour on the brand colour (automatic picks white while the contrast stays 3:1 or more), 16 ready palettes that fill both colours in one click, and a live demo (header, menu, tabs, buttons, chart, field, e-mail button). Use the brand colour on the whole site and both panels (on by default) makes it the accent everywhere, charts included; off = only e-mails and status pages use it.
  • E-mail: driver (PHP mail or SMTP), from address and name, SMTP host, port, user, password (encrypted), encryption and certificate verification, a mail footer, a switch to disable all mail, and a test-mail button.
  • SMS & WhatsApp: SMS provider (Disabled sends nothing): RT Communications (Bangladesh, rtcom.xyz) needs the Account code (the acode on your portal.rtcom.xyz panel), the API key (encrypted) and the Approved sender / mask; Message type is Transactional (alerts, codes) or Promotional (needs the approved Template ID, shown only then). Bengali text is sent as Unicode automatically, and a message counts as sent only when RT answers code 200 - a low balance (code 301) is logged as a failure. Twilio, Vonage and Textbelt need their own keys and always get the number as +E.164; a custom HTTP gateway takes a GET/POST URL with {to} {text} {key} {sender} (also {to_e164}, {to_plain}), headers, a POST body (JSON, query string or one name=value per line) and an optional success text. Country calling code (880 for Bangladesh; 88 is read as 880) is put in front of local numbers, whose leading 0 is dropped; + or 00 marks a number as international. Number format the gateway wants (RT and custom gateways): Country code, no plus (8801711223344), with a plus (+8801711223344) or As dialled at home (01711223344) - the examples follow the country code as you type. WhatsApp provider: GREEN-API (create an instance at green-api.com, scan its QR code with the phone that sends; enter the Instance id, the API token instance and the instance's own API URL, e.g. https://7103.api.greenapi.com; messages go to <number>@c.us), the Meta Cloud API (phone number id + access token) or a custom HTTP gateway. Each card shows N sent, M failed and the last error from the message log. Check it works: send a test SMS / WhatsApp (save first; the words come from the Provider test template), Check the connection & balance (RT Communications: balance and credit; Twilio, Vonage, Textbelt: the account) and Check the connection (GREEN-API: whether the instance is authorized, not yet scanned, starting, asleep because the phone is offline, blocked or suspended). The provider's raw answer of every send is kept in the message log. Buttons at the top lead to Message templates, Send message and Message log (below).
  • Security: allow private targets, trust proxy headers (behind Cloudflare or a reverse proxy), audit retention days, social sign-in (Google, GitHub) keys, maintenance mode with its message (visitors and users see the message; staff, the API, cron and probes keep working).
  • Monitoring: worker seconds per cron run, probe poll seconds, probe self-update on/off, the region label of the main server, default confirmations for new monitors.
  • SEO (2.1.1, in sub-tabs): Global (title format with {page} {sep} {site} {tagline}, home title and description, keywords, default robots rule, canonical host www / non-www, force https, a whole-site noindex switch for a staging copy); Social (Open Graph image, type and locale, Twitter/X card and @handle, Facebook app id); Verification (Google, Bing, Yandex, Baidu, Pinterest codes - a pasted <meta> tag is reduced to its code - and extra head HTML); Analytics (GA4, Tag Manager, Meta Pixel, Clarity, loaded on public pages only and, with the cookie banner on, only after the visitor's OK; plus a free analytics snippet, public pages only); Structured data (Organization with logo and social profiles, WebSite, SoftwareApplication with the plan prices, breadcrumbs, articles); Pages (title, description and noindex for every fixed public page; blog posts and pages have their own SEO fields); Sitemap (an automatic sitemap index /sitemap.xml with /sitemap-main.xml, -pages, -posts, -docs, -status and optional -monitors, change frequency and priority per section, exclusions with *, rebuilt when content changes, every hour and with Regenerate now, a readable /sitemap.xsl, and IndexNow for Bing/Yandex with its key file); robots.txt (generated rules plus extra lines, an optional block on AI crawlers, or a full custom file, with a preview); SEO check (problems, warnings and tips with links).
  • Licence: the licence key and the licence server (LCPanel, https://lcpanel.com).

The key for the web-cron URL is shown and can be rotated on System health.

E-mail & templates: every e-mail the platform sends as an editable template (subject and HTML body with {placeholders}): welcome, verify e-mail, reset password, two-factor code, new device, admin new user, team invitation, monitor down/up/degraded, SSL and domain expiry, server offline/online/alert, incident update, status page subscription and incident, scheduled report, invoice, payment received/rejected, renewal reminder, contact reply, admin contact message, probe offline and a test mail; 2.1 adds Agency: client payment to approve, Enterprise quote received, Admin: enterprise quote and Enterprise plan ready. Templates are wrapped in a branded frame; a template can be switched off.

Since 2.1.1 templates can be added (a code such as my_notice, sent from code with mail_send_template('my_notice', $to, array(...))), edited, duplicated and deleted (only your own; built-in ones are reset instead). The editor shows the placeholders you can click in and a live preview (desktop / phone, light / dark) that follows every key you type; Send preview to me mails it to you. The Layout tab designs the frame around every mail: the header (mail, light or dark logo or the site name as text, logo height, colours, alignment, padding, a line of text), the body (background, card, border, text, button and link colours, font, size, corner radius, width), the footer (site name, address, e-mail, phone, social links, copyright, a note, free HTML, colours) and dark mode (a dark logo and colours for mail apps that support it). An empty design looks like the earlier mails.

Message templates (/admin/message-templates): every SMS and WhatsApp text the platform sends (monitor down/up/degraded, escalation, SSL and domain expiry, content and DNS changes, flapping, grouped alerts, server offline/online/alert/service/reboot, integration errors, the test message, and starter texts for manual messages), grouped by event, with length, encoding (GSM-7 or Unicode) and SMS parts. The editor has a phone and a WhatsApp preview that follow your typing, placeholders to click in and Send sample; add your own, delete them, reset built-ins. Until a built-in text is edited the alerts keep their old words.

Send SMS / WhatsApp (/admin/message-send): a manual message to typed numbers, chosen users, every user with a phone, or the users of a plan, optionally from a template, with {name}, {email}, {phone}, {site_name}, {site_url} filled per person. Up to 5 go out at once, more are queued; at most 500 per send and 1000 per hour (settings msg_manual_max, msg_manual_hourly). Message log (/admin/message-log): every SMS and WhatsApp (alerts, tests, manual) with status and the provider's answer, filters, a 30-day chart, CSV export and Send again for failed ones.

Licence: the licence key, its state as reported by the licence server LCPanel (https://lcpanel.com), the addons it includes, and re-check / activate actions, plus links to the product page, changelog, documentation and your client area on lcpanel.com. Keys from the old license.faruk.bd no longer work: get a new one at https://lcpanel.com/user/licenses.php. The footer credit follows the licence.

Modules (plugins) (on the Licence page, 2.1.3): every module the installation runs - Brand colours, Server monitoring, Diagnostics, Intelligence, Synthetic monitoring, Protocol monitors, Agency & reseller, Mobile & push, SMS & WhatsApp templates, Payment methods, SEO & analytics, E-mail templates - with what it adds, the version it came with, links to its pages and its file in includes/ext. Active = loaded on this request; Missing = the file was not uploaded with the update (upload the full update ZIP again); Extra file = a module file the catalogue does not know. In licence marks the add-ons your LCPanel licence lists; all modules are built in and free with the script.

Support sign-in from LCPanel: the licence owner's support can press Login as admin on lcpanel.com. The browser opens /admin/license-login.php with a one-time link; this site asks lcpanel.com whether the link is real, unused, not expired and made for this licence and domain, and only then signs in the first active administrator. A used, expired or foreign link shows the reason and signs nobody in; every sign-in is in the audit log (license.support_login). LCPanel can switch the bridge off in its settings.

AI assistant (/admin/ai): the optional assistant that writes incident and report summaries.

  • Enable the AI assistant, the Anthropic API key (stored encrypted; Remove the key deletes it), the Model (Claude Haiku 5.5 or Claude Sonnet 5.5, with prices per million tokens), the API base URL (empty = the Anthropic API; change only for a proxy or a test stand-in) and the Monthly call cap (all organisations) (0 = no cap). Plans can also limit calls per organisation with AI calls / month.
  • Test connection sends one short request (it counts as a call).
  • Stat cards show the status, calls this month and the estimated cost from token usage; tables list usage this month by organisation (answered / attempted calls, tokens, cost) and the latest calls.
  • Intelligence tuning sets the rule-based features: correlation window, flapping (status changes within minutes, stable again after), anomaly sensitivity k, samples in a row, minimum ms above normal, and baseline history days. Empty fields use the defaults shown.

Only monitor names, types, targets without credentials or query strings, error texts, timings and the incident timeline are sent; every answer is labelled as an AI suggestion. See Intelligence.

Mobile apps (/admin/mobile-apps): the installable web app, Web Push (VAPID keys, device counts, message lifetime, devices per user) and the Android / iOS project downloads with their settings and build steps. See Mobile app and push.

এই পেজটি কি সহায়ক ছিল?

একটি ক্লিক আমাদের এই ডকস উন্নত করতে সাহায্য করে।

এই পেজ শেয়ার করুনসাধারণ লিংক - কোনো ট্র্যাকার নেই, ক্লিক না করা পর্যন্ত কিছু লোড হয় না।