Manual coverage

How to read the status

This page prevents an available guide from being mistaken for complete product documentation. A macro-area is complete only after its pages, actions, fields, statuses, permissions, variants, integrations, and error cases are inventoried and documented in both languages.

• To inventory: the area is known, but its detailed inventory is incomplete.
• Under analysis: interface, routes, controllers, and views are being examined.
• Draft: content exists but is not exhaustive.
• Verified: the specific procedure was reproduced in the browser and compared with code.
• Not reproducible: documented from code or a diagram, with the limitation stated.

ISP administration

Overall status: coverage complete. The manual inventories Dashboard and settings; CRM, suppliers, resellers, contracts, quotes, and activities; service catalog and provisioning; invoicing, payments, accounting, and Aruba FE; warehouse, ecommerce, exports, and requirements; tickets and communications; VoIP and providers; Radius and network management; coverage and wholesale operators; security, infrastructure, gateways, and OTP signatures.

Routes, controllers, and views were reconciled with the Italian and English articles for every family. Reproducible procedures were exercised in the browser; workflows depending on unavailable provider accounts or data are described from implemented behavior without presenting an unperformed test as successful.

Customer Area web

Overall status: coverage complete. The guide separates authentication, credential recovery, and profiles; Home; invoices, PDFs, and payments; ordinary and rechargeable services; OTP termination; tickets; notifications; quotes; contracts; profile, automatic payment methods, and documents. The Shop is documented as a separate journey covering catalog, cart, addresses, delivery, checkout, and orders.

Principal journeys were verified with a demonstration account, including a Stripe test payment, rechargeable-service period update, and ticket lifecycle. States, permissions, and ISP dependencies remain documented even when a particular profile cannot access a feature.

ISP App and mobile interface

Overall status: coverage complete. The manual covers provider code, branded login and persistent session, profile switching, Home, invoices and payments, services and termination, tickets, notifications, quotes, profile, documents, VoIP, Shop, and the reseller workspace.

Mobile functions were compared separately from their web equivalents. Native captures retain phone proportions and clearly distinguish the customer, ISP operator, and reseller experiences delivered by the same application.

Reseller Area

Overall status: coverage complete. The manual covers setup and permissions, account association, customers and services, warehouse, commissions, statements and payments, credit balance, customer invoices, gateways and rechargeable services, coverage, and the complete contract-creation workflow.

The guides distinguish exclusive and non-exclusive visibility, data ownership, effects on the end customer, and precedence of economic rules. Administration pages, desktop portal, and mobile workspace were verified as separate surfaces.

APIs, webhooks, and automation

Sixteen public OpenAPI specifications cover customers, groups, custom fields, invoices, payments, services, instances, ISP Radius 2.0, warehouse, activities, and teams. The API guide explains keys, permissions, IP whitelists, authentication, pagination, requests, responses, and interactive-console testing.

Webhooks and scheduled jobs are documented with their consuming modules, separating operator configuration, automatic execution, retries, outcome verification, and operational effects.

Completion and maintenance criteria

• Menus, pages, and role variants inventoried
• Actions, confirmations, fields, and dependencies explained
• Statuses, transitions, permissions, and visibility documented
• Normal, alternative, and foreseeable error workflows covered
• Relevant real screenshot or stated limitation
• Related APIs and automation documented with the module
• Equivalent Italian and English content
• Desktop and mobile browser verification
• Search, links, images, and indexing checked

Current coverage satisfies these criteria for the published areas. Every future change to interfaces, features, providers, APIs, or automation must update both languages in the same work and replace screenshots that have become inaccurate.