Written guide
Overview
Appmint System Operations is the platform administrator’s view across organizations. We will inspect a controlled organization, follow a job from its details to its outcome and understand service configuration without treating platform-wide actions as everyday company settings.
Access and navigation before any change
Concept illustration: System Operations is for authorized platform administration. A platform-wide recovery action is not a shortcut for repairing one business record. This is not an application screenshot or evidence that the action has run.
Use your authorized platform account in the deployment's system organization. Organization Owner access for an ordinary business is not the same context. If the page says System Operations isn't available here, verify the selected organization with the platform administrator; do not treat its missing tables as an outage or try another company's ID.
Sidebar labels and the tabs inside the console differ slightly:
| Sidebar entry | Console section | Use it for |
|---|---|---|
| System Monitoring | Monitoring | Read system health and measurements |
| Queue Manager | Queue | Inspect a specific job and its error |
| Domain Mapping | Domains | Inspect organization/site routing |
| Service Pricing | Services | Define service calculation and agreement |
| Usage & Credits | Usage & Credits | Inspect credit and configured charged paths |
Service Usage is also available inside the console; it explains which organizations used services and the recorded cost/billing behind them. Inspect before editing: choose one known organization, retain its ID, and compare the same record after refresh. No matching retained System Operations screenshot was available in this review; these names are checked against the current UI source, not a freshly executed administrator session.
1. Enter the system organization and read monitoring
Why this matters
This screen is restricted to the platform system organization. Seeing an access notice in an ordinary business account is expected, not a missing-data dashboard.
Follow these steps
Sign into the authorized system organization and open System Operations. Read Overview and System Monitoring. Inspect resource data, registrations, user/web activity and alerts. Use the named sections to navigate; retain unavailable/error states rather than replacing them with zero. Identify the organization affected before every write.
Check the result: The operator distinguishes valid measurements, missing data and an access restriction.
2. Inspect and recover a queue job
Why this matters
A queued item contains its own payload, attempts, progress and retry information. Retry can execute the action again, so choose a controlled job whose side effects are understood.
Follow these steps
Open Queue Management. Filter All, Active, Pending, Completed or Failed and narrow to the intended queue/job. Open a prepared failed item and inspect payload, priority, attempts/max attempts, progress, next retry and error. Correct its known cause before Retry. Refresh and inspect both queue state and the target record/action. For a separate pending disposable item choose Cancel and verify the state. Demonstrate Retry Selected and Cancel Selected only after reviewing every checked item; do not bulk-retry unknown production jobs. Failed-job cleanup removes diagnostic history and is separate from resolving its cause.
Check the result: Job state and the intended side effect agree, including partial/repeated execution checks.
3. Manage organizations and accounts in the right scope
Why this matters
Company records, organization users and customers are related but different. A platform-wide administrator must keep the chosen organization visible during account operations.
Follow these steps
Open Companies and locate the controlled organization. Inspect account status, owner/contact information, limits and addresses. Edit only the intended field, save and reopen. Inspect its sites/development environments, plan, subscription, billing transactions and account history as their own data. Open Org Accounts, explicitly select that same organization, then choose its Users or Customers. Inspect the target identity before a status change or controlled password-reset action. Verify the resulting account state in that organization; reset delivery needs a controlled inbox.
Check the result: The edited company/account belongs to the intended organization and persists after refresh.
4. Configure and verify a domain mapping
Why this matters
A platform mapping specifies organization, site and host organization. It is not proof that public DNS resolves or that a certificate is ready.
Follow these steps
Open Domain Management, search the domain and inspect the existing mapping. On a controlled mapping enter Domain, Organization, Host Organization, Site Name, Type and Status as exposed by the form. Save and reopen. Test the actual public address and compare the organization/site returned. If it resolves elsewhere, inspect both mapping and DNS rather than modifying an unrelated organization.
Check the result: Stored mapping and public resolution agree; pending DNS/TLS remains separately identified.
5. Define a service and its billing configuration
Why this matters
Service identity, provider operation and pricing are separate choices. The pricing display text is a label, not the calculation itself.
Follow these steps
Open Services and search the intended service. Create or edit a controlled entry. In General enter Service Name, Display Title, Provider, Operation, Status, Requires Agreement and Description. Blank Operation applies broadly according to the current hint, so prefer the precise operation where intended. In Pricing choose Billing Model, Cost Source, Currency and Billing Interval. Set Price or the applicable Unit Name, Unit Size and Unit Price. Enter Pricing Display consistent with those values. In Markup choose its type and percentage or fixed amount as appropriate. For tiered pricing configure Tier Period and the actual tier boundaries/rates, then inspect the saved tiers. Save and reopen every changed section.
Check the result: The service identity and pricing structure persist; no actual charge is claimed from a configuration save.
6. Agreements, documentation, credits and charged paths
Why this matters
Service agreements are shown to customers. Credits and charged service paths affect operation and accounting, so demonstrations use a documented controlled adjustment.
Follow these steps
In the service’s Agreement & Documentation section enter the intended Agreement Text and Documentation HTML. Inspect Config Version under System: the hint states higher code versions may update records on startup, so account for that when diagnosing changed configuration. Avoid Initialize Default Services or Delete All Service Pricing as ordinary setup shortcuts; inspect their confirmations and scope without executing against live data. Open Usage administration. In Organization credit search the controlled organization and inspect its balance and service costs. For an explicitly authorized small test use Gift Credits, enter the amount and a clear note, submit once and verify the balance/history. In Charged services use Add charged service, enter the exact service path and configured amount/unit information, save and reopen. Verify any actual usage charge against a controlled service invocation and its ledger. Never infer a charge merely from a configured path.
Check the result: Administrative writes have persisted records and their runtime/ledger outcomes are checked separately.
7. Account lifecycle, plan changes and explicit user password options
Why this matters
Ownership transfer, a company email change and account cancellation are separate administrative actions. Each needs the exact target and a reason; a reset-email notice also needs delivery verification.
Follow these steps
Open the controlled company’s drawer and inspect Overview, Sites, Billing and Plan. In Plan inspect the current catalogue-backed plan choices rather than typing an invented plan key. For an authorized change choose the intended Plan and Status, enter Reason, submit once and reopen the record/history. Compare Active, Trial, Grace, Inactive, Suspended and Expired as distinct states rather than using them interchangeably.
In the company’s lifecycle controls inspect New Owner Email and Reason for ownership transfer, and New Email and Reason for changing company email. Re-read the company after any authorized controlled action. For cancellation inspect Reason and Confirm Email and cancel the dialog during a non-destructive demonstration. Distinguish cancellation/reactivation, deleting a company record and deleting organization infrastructure; do not use deletion as a substitute for suspending an account.
In Org Accounts select the controlled organization and Users or Customers. When creating an account, either set an initial password in the optional field or leave it blank for the set-password-link path. The UI checks at least six characters for an administrator-supplied password; that is not proof that every effective password-policy rule is enforced by this form. After creation verify the account record and test the controlled recipient’s actual inbox. For an existing account use its password panel to set an authorized test password or Send password-reset email for the delivery flow. Keep passwords/tokens out of capture. Delete only a disposable account after reviewing its confirmation.
Check the result: The company/account lifecycle state and any delivered reset link match the intended operation.
Source-confirmed finding: Blank-password account creation catches and ignores sendReset failures but can still show a set-password-email-sent notice. Therefore the course must check the inbox and log delivery failures; the notice is not proof. Pricing alternatives available in the current editor are Free, One Time, Recurring, Per Use, Per Unit and Tiered; Cost Source is Fixed or Provider (Dynamic). Test their calculations individually before making accounting claims.
8. Trace service usage to the organization and charge
Service configuration explains what should be billed; Service Usage shows recorded uses, cost and billing. A charge recorded against an organization is not necessarily collected money, and an absent cost is not evidence that the provider supplied the operation free.
- Open System Operations, then Service Usage inside the console. Select the period before interpreting totals; the initial period is this month.
- Read Billed to orgs, Our cost, Margin, Uses with no cost recorded and Orgs needing attention together. Keep a loading/error notice distinct from a genuine report with no activity. Use Try again for a load failure or Refresh for a new read.
- In By service, select the relevant service to narrow the organizations below. Search for the intended organization and open its detail. Keep the same period as the overview.
- Inspect its service breakdown, then the underlying charges. Compare service/provider/operation, amount and the shown cost source: provider cost and catalog rate are different inputs. Use charge pagination when the period contains more than the visible rows.
- Return using Service Usage in the detail header. If the report identifies missing agreement, debt or refusal, investigate that exact organization and service; do not gift credits, retry jobs or alter a pricing rule just to clear an indicator.
The result of this read-only check is a traceable organization/service/charge reference. Calculating margin from recorded values does not verify bank settlement or prove that a provider's invoice was reconciled. Keep missing cost and failed collection as separate follow-up items.
Troubleshooting and recovery
Read the actual error and inspect persisted state before retrying a create or other write. Keep the selected organization, record and operation visible. A saved configuration, permission, provider connection and working consumer are separate checks; verify the one the lesson claims. Reopen after saving and compare a controlled alternate/failure path where the chapter calls for it.
Next steps
You can now follow the module’s setup and check its result. Use the relevant chapter for an alternative, and verify the actual consumer before treating configuration as complete.
Limitations and checks
Current system-org guard, Queue Management, Services and Usage Admin controls inspected with catalogue source references for related management screens. Platform-wide changes, charges, credits, password resets and retries were not executed. Monitoring/provider and accounting correctness require authorized controlled live proof. The course is for platform admins, not ordinary business-user onboarding.