SolarOps Tenant User Manual

Version: 1.1 release-readiness candidate Date: 2026-07-18 Audience: SolarOps subscriber administrators, office users, warehouse users, technicians and field users Authorised example tenant: Sorted Verification basis: Authenticated production-hosted UAT. No other tenant was modified.

> Release notice: The authenticated platform account did not expose a Sorted tenant membership in the account chooser, so tenant-only workflows remain Blocked or Not Tested. Public pricing and the authorised Zoho demo expense were browser-verified and captured. Billing lifecycle repairs are verified in source and automated tests but are not deployed, migrated or proven by Paystack Test payment events.

How to Read This Manual

Each section states its UAT status. A Passed result was completed in the browser. Partially Passed means only the stated portion was verified. Blocked means access or an integration prevented the workflow. Not Tested means no browser claim is made.

Warnings:

1. Do not use real customer details in training records. 2. Prefix training records with MANUAL-UAT -. 3. Do not send email or WhatsApp messages during training unless the recipients are approved test destinations. 4. Do not receive, allocate or consume stock unless the warehouse owner has approved the test. 5. Treat public pricing, source tests, deployed configuration and payment-event evidence as separate verification layers.

Contents

1. Welcome to SolarOps 2. Public Website 3. Account Access 4. Dashboard 5. Navigation 6. Clients 7. Projects 8. Leads, Quotations and Sales 9. Job Cards 10. Inspections and Site Reports 11. Deliveries 12. Product Catalogue 13. Inventory 14. Barcode and QR Scanning 15. Global Search 16. Support Tickets 17. Warranties 18. Documents and Reports 19. Communications 20. Zoho Integration 21. Company Settings 22. Users, Roles and Permissions 23. Mobile Field Workspace 24. Client Portal 25. Troubleshooting

1. Welcome to SolarOps

UAT status: Partially Passed

Purpose. SolarOps brings client, project, field-work, stock, document, support, warranty and billing information into one tenant workspace. The usual operating flow is client -> project or sale -> stock and field work -> documents and handover -> support and warranty.

Who uses it. Tenant administrators control company settings and access. Office users manage clients, projects and commercial records. Warehouse users manage products and stock. Field users work with job cards, inspections, deliveries, photos and signatures.

Before you begin. Confirm the company shown in the account chooser. SolarOps platform administration is separate from subscriber workspaces and is available only to authorised platform staff.

Steps.

1. Sign in through SolarOps. 2. Choose the correct company from the account chooser. 3. Confirm the company name before creating or changing records. 4. Use the tenant navigation to open the required workspace. 5. Save once, then verify the new or changed record before continuing.

Expected result. The selected tenant opens and only records belonging to that tenant are visible.

Screenshot. The account chooser was captured, but no Sorted tenant dashboard screenshot exists because the signed-in account had no tenant membership.

Common problems. A platform-only user may see only the protected platform context; direct tenant URLs are not a substitute for membership. A 404 on /sorted was reproduced with the platform-only account.

Related features. Account access, navigation, users and roles.

Permissions. A current active tenant membership is required.

Mobile notes. Mobile navigation and field controls require a separate 390 x 844 retest.

2. Public Website

UAT status: Passed for pricing; other public flows Not Tested

Purpose. The public site explains SolarOps, presents packages and offers, provides legal and knowledge-base links, and directs visitors to sign in or register.

Who uses it. Prospective customers, existing users and support visitors.

Before you begin. Prices exclude VAT where the pricing card says so. Checkout is expected to be in ZAR; displayed USD amounts are approximate marketing references only.

Steps.

1. Open https://www.solarops.cloud/pricing. 2. Review the five public packages: Solo, Starter, Growth, Professional and Enterprise. 3. Use the Monthly and Annual controls and confirm the displayed ZAR amount, 14-day trial, limits and feature summary. 4. For monthly launch pricing, confirm that the lower price applies to the first three successful billing cycles and that the standard monthly price is disclosed. 5. Confirm the launch-pricing window reads 18 July 2026 to 31 December 2026. 6. Use Read more to inspect additional features and add-ons; use Show less to collapse the card. 7. Select a plan only when Test checkout has been approved and the deployed provider mapping is verified. 8. Use Knowledge Base, Privacy Policy, Terms of Service and Refund Policy for supporting information.

Expected result. Exactly five configured packages are public. Growth is featured as Recommended; Professional shows Priority support; Enterprise shows Custom SLA. The hidden legacy Trial package does not appear as a package card.

Screenshot.

Screenshot captured: SolarOps public pricing showing five packages and launch pricing active through 31 December 2026.

Common problems. Public display does not prove that a provider mapping is deployed or that Test payment events have completed. The source implementation now tracks three successful introductory cycles and prepares a standard-plan transition, but this pass did not migrate or deploy it.

Related features. Registration, packages, promotions and billing.

Permissions. Public access.

Mobile notes. Mobile pricing was not captured or verified at 390 x 844.

3. Account Access

UAT status: Partially Passed

Purpose. Account access protects tenant data and directs a user to the correct platform or company context.

Who uses it. Every SolarOps user.

Before you begin. Use your own approved account. Never share passwords or one-time codes.

Steps.

1. Open the SolarOps sign-in page. 2. Enter your approved sign-in details. 3. At /account, select the required company. Platform staff may also have a separate protected administration context. 4. Confirm the context before continuing. 5. Use My Account for available security settings. 6. Use Sign out when working on a shared device.

Expected result. The account chooser lists only contexts the user may access. In this pass, the signed-in platform administrator opened the protected administration context but had no Sorted tenant option.

Screenshot. Not captured.

Common problems. Incorrect company options indicate a membership or access configuration issue. Password reset, invalid login, inactive-user handling, PWA installation and multi-company tenant switching were not tested.

Related features. Users, roles, tenant isolation and troubleshooting.

Permissions. An active user account and active membership.

Mobile notes. Sign-in and account selection require mobile retesting.

4. Dashboard

UAT status: Blocked

Purpose. The tenant dashboard should summarise projects, job cards, support, warranties, invoices, stock warnings and recent work.

Who uses it. All tenant roles, with content controlled by permission.

Before you begin. Confirm the tenant name and reporting period.

Steps. The exact tenant dashboard procedure is withheld until the Sorted dashboard can be opened with an authorised tenant membership. During retest, verify summary cards, pipeline, alerts, notifications, quick create, search, active projects, job cards, support and warranties.

Expected result. Each card links to tenant-scoped records and respects role permissions.

Screenshot. Required: tenant-01-dashboard-desktop.png and tenant-01-dashboard-mobile.png; not captured.

Common problems. Blank or zero cards may reflect filters, permissions or no data. A direct 404 is an access problem, not a zero-data dashboard.

Related features. Navigation, search, projects, support and inventory.

Permissions. Tenant membership plus module permissions.

Mobile notes. Verify card stacking, menu access and no horizontal overflow at 390 x 844.

5. Navigation

UAT status: Blocked

Purpose. Navigation groups work into Workspace; Projects and Operations; Products and Inventory; Support and Warranty; Clients and Partners; Documents and Reports; Accounting and Integrations; Company Administration; Settings; and Users and Roles where enabled.

Who uses it. All tenant users.

Before you begin. Menu visibility may be controlled by the package and role.

Steps. Tenant menu labels and routes were not browser-verified. During retest, open every visible desktop entry, repeat on mobile, and confirm direct-route protection for hidden modules.

Expected result. No duplicate, dead or cross-tenant links; hidden pages remain protected when entered directly.

Screenshot. Not captured.

Common problems. A missing entry may be a package entitlement or permission issue. A visible entry that returns 404 is a navigation defect.

Related features. Packages, roles and mobile workspace.

Permissions. Vary by module.

Mobile notes. The complete mobile menu remains unverified.

6. Clients

UAT status: Blocked

Purpose. Client records centralise business or individual contacts, sites, notes, projects, sales, assets, warranties, support history and communication actions.

Who uses it. Sales, office, project and support users.

Before you begin. Prepare fictional UAT contact details and avoid real phone numbers or email addresses.

Steps. Do not follow unverified field instructions. Retest must create MANUAL-UAT - Client, choose the client type, add one fictional site, save, reopen, search and inspect related tabs without sending communications.

Expected result. One tenant-scoped client is created and searchable; related records remain empty until explicitly linked.

Screenshot. Required create and detail screenshots; not captured.

Common problems. Duplicate clients, missing site selection and hidden communication actions require bug records.

Related features. Projects, quotations, assets, support and warranties.

Permissions. Client view/create/edit permissions.

Mobile notes. Verify long addresses and action menus wrap without horizontal overflow.

7. Projects

UAT status: Blocked

Purpose. Projects coordinate a client site, manager, team, dates, commercial documents, procurement, stock, job cards, inspections, deliveries, photos, handover, support and warranty links.

Who uses it. Project managers, office users, warehouse users and technicians.

Before you begin. A test client and site are required.

Steps. Retest must create MANUAL-UAT - Project, link the UAT client and site, set dates and status, save, reopen, add no real commercial transaction, and verify each visible project workspace tab.

Expected result. The project reference is unique, appears in search and exposes only enabled modules.

Screenshot. Required create, detail and mobile project screenshots; not captured.

Common problems. Missing client/site options, stale status, broken thumbnail, inaccessible tabs and unlinked downstream records.

Related features. Clients, job cards, inspections, deliveries, documents and stock.

Permissions. Project view/create/edit and related module permissions.

Mobile notes. Verify project tabs collapse into an accessible mobile pattern.

8. Leads, Quotations and Sales

UAT status: Not Tested

Purpose. These workflows should convert enquiries into accepted work or supply-only sales while preserving an audit trail.

Who uses it. Sales, finance and authorised administrators.

Before you begin. Use fictional records and do not post a real invoice, payment or accounting transaction.

Steps. Exact controls are withheld. Retest should cover lead creation, enquiry history, quotation, acceptance, sale, purchase order, pro forma, tax invoice, stock allocation and asset creation only in approved UAT data.

Expected result. Status changes are explicit and no financial document is duplicated or posted externally without confirmation.

Screenshot. Not captured.

Common problems. Missing tax settings, duplicate numbering, stock allocation before approval and unintended accounting sync.

Related features. Clients, projects, inventory, documents and Zoho.

Permissions. Commercial and accounting permissions.

Mobile notes. Complex commercial editing should be checked for responsive tables and action menus.

9. Job Cards

UAT status: Blocked

Purpose. Job cards assign scheduled field work to a user or technician and collect instructions, notes, photos, inventory usage, signatures and completion evidence.

Who uses it. Coordinators, technicians and project/support users.

Before you begin. Prepare a UAT project or support ticket and an approved assignee.

Steps. Retest must create MANUAL-UAT - Job Card, link only the UAT source record, schedule it, save, reopen, test status changes, add fictional notes, generate the PDF and avoid sending communication actions.

Expected result. The job card keeps its link, assignee and status; PDF output is complete.

Screenshot. Not captured.

Common problems. Unavailable service choices, missing assignee, inventory deduction without confirmation, signature loss and PDF clipping.

Related features. Projects, support, inventory, documents and scanning.

Permissions. Job-card view/create/assign/update permissions.

Mobile notes. Field status, photos and signatures require 390 x 844 testing.

10. Inspections and Site Reports

UAT status: Not Tested

Purpose. Inspections capture checklists, notes, photos and signatures and produce a shareable site report.

Who uses it. Inspectors, project managers and technicians.

Before you begin. Confirm inspection type, client/project and approved fictional content.

Steps. Exact labels are withheld. Retest must create a draft inspection, complete the checklist, add a safe image, sign with a fictional mark, complete it and inspect every PDF page at full width.

Expected result. The report includes company branding, QR code, images and signatures without clipping the right side.

Screenshot. Not captured.

Common problems. Cut-off PDF content, missing logo, broken image preview, missing QR code and premature completion.

Related features. Projects, documents, communications and mobile workspace.

Permissions. Inspection create/complete/report permissions.

Mobile notes. Camera and signature controls require device-size testing.

11. Deliveries

UAT status: Not Tested

Purpose. Delivery records track items, serial numbers, loading, proof of delivery, signatures and delivery documents.

Who uses it. Warehouse, logistics and project users.

Before you begin. Use approved UAT stock only. Do not alter real stock.

Steps. Retest must create MANUAL-UAT - Delivery, link the UAT project/client, add only UAT items, verify serial handling, save a draft, inspect delivery-note output and do not send email or WhatsApp.

Expected result. Stock and delivery status remain consistent and the proof-of-delivery record is tenant-scoped.

Screenshot. Not captured.

Common problems. Duplicate serials, stock changing before dispatch, missing signature and inaccessible report.

Related features. Inventory, projects, scanning and documents.

Permissions. Delivery and stock permissions.

Mobile notes. Loading, proof photos and signature capture require mobile testing.

12. Product Catalogue

UAT status: Not Tested

Purpose. The catalogue defines product types, models, brands, images, datasheets, prices, tax behaviour, serialisation, batches, services and accounting references.

Who uses it. Product administrators, procurement, warehouse and accounting users.

Before you begin. Confirm whether the item is a stock product, serialised item, batch item or service.

Steps. Retest must create MANUAL-UAT - Product Model, use fictional model and barcode values, save, reopen and verify images, pricing and accounting references without synchronising external data.

Expected result. The model is available to approved inventory and commercial workflows.

Screenshot. Not captured.

Common problems. ProductItem/ProductModel confusion, duplicate barcode, missing type/category, failed image preview and unintended Zoho linking.

Related features. Inventory, scanning, sales and Zoho.

Permissions. Product configuration permissions.

Mobile notes. Verify forms, images and long model names at 390 x 844.

13. Inventory

UAT status: Not Tested

Purpose. Inventory controls warehouses, locations, receipts, quantities, serials, batches, quarantine, allocations, picking, packing, installation, assets and warranty activation.

Who uses it. Warehouse, logistics, project and authorised inventory administrators.

Before you begin. Obtain approval before any quantity-changing action. Use UAT-only items and locations.

Steps. Retest should set up a UAT location, receive MANUAL-UAT - Stock Receipt, inspect serial/batch validation, move or allocate only the test quantity, and reconcile stock history after every action.

Expected result. Every quantity movement has an auditable source and destination; duplicates and negative stock are prevented.

Screenshot. Not captured.

Common problems. Incorrect product ownership, duplicate serials, stock mismatch, missing history and allocation without available quantity.

Related features. Products, projects, deliveries, installations and warranties.

Permissions. Warehouse and stock transaction permissions.

Mobile notes. Scanner, tables and quantity controls need mobile verification.

14. Barcode and QR Scanning

UAT status: Not Tested

Purpose. Scanning should find or count records without requiring manual entry.

Who uses it. Warehouse and field users.

Before you begin. Grant camera permission only for the SolarOps site. Use fictional UAT codes.

Steps. Retest must open the visible scanner, grant permission, scan product/serial/project/job-card/support/warranty/inspection/delivery/quotation/invoice/handover/client references, test duplicate handling, close the scanner and confirm the camera stream stops.

Expected result. Each supported code opens the correct tenant record and closing releases the camera.

Screenshot. Not captured.

Common problems. Permission denied, camera remains active, duplicates increase quantity, unsupported code and hardware scanner focus loss.

Related features. Inventory, search and mobile workspace.

Permissions. Scanner plus target-record permissions.

Mobile notes. This is primarily a mobile workflow and remains unverified.

15. Global Search

UAT status: Not Tested

Purpose. Global search should find records by business identifiers, not merely filter dates.

Who uses it. All authorised users.

Before you begin. Know one approved UAT value for each tested record type.

Steps. Retest should search client name, phone, email, project/ref, serial, barcode, QR value, invoice, quote, support, warranty, inspection, delivery, job card, product, document and handover file.

Expected result. Results are tenant-scoped, permission-aware and open the correct record.

Screenshot. Not captured.

Common problems. Date-only filtering, stale index, cross-tenant results, partial reference mismatch and hidden result after navigation.

Related features. Every record module.

Permissions. Search plus permission to view each result.

Mobile notes. Verify keyboard, result list and long references.

16. Support Tickets

UAT status: Blocked

Purpose. Support tickets manage a request from creation through assessment, assignment, appointment, field work, repair, communication, sign-off and closure.

Who uses it. Support agents, technicians, managers and authorised client users.

Before you begin. Use a UAT client/project/asset. Decide whether work is free, chargeable, in warranty or requires inspection.

Steps. Retest must create MANUAL-UAT - Support Ticket, set priority and links, assign a test user, add a note, create a linked UAT job card if available, test resolution and closure, and avoid real messages.

Expected result. The lifecycle remains auditable and linked stock/labour/travel entries are explicit.

Screenshot. Not captured.

Common problems. Invalid status transitions, missing assignment, duplicate job cards, stock deductions and closure without sign-off.

Related features. Job cards, warranties, assets, documents and communications.

Permissions. Support view/create/assign/update/close permissions.

Mobile notes. Support visits and photo/signature capture require mobile testing.

17. Warranties

UAT status: Not Tested

Purpose. Warranty records connect product defaults, installed assets, activation, customer claims, supplier claims, repair, replacement, rejection and closure.

Who uses it. Support, service-centre, warehouse and project users.

Before you begin. Use an approved UAT asset and fictional serial number.

Steps. Retest should confirm defaults, register MANUAL-UAT - Warranty Claim, link the UAT asset/support/job card, add fictional evidence, test permitted decisions and verify closure.

Expected result. Claim history and outcome remain linked to the asset and tenant.

Screenshot. Not captured.

Common problems. Incorrect warranty dates, missing supplier link, duplicate claims, broken asset relationship and unapproved replacement stock.

Related features. Inventory, assets, support, job cards and documents.

Permissions. Warranty and related module permissions.

Mobile notes. Evidence capture and status controls need mobile testing.

18. Documents and Reports

UAT status: Not Tested

Purpose. The document area stores files and generated quotations, invoices, inspection reports, delivery reports, handover packs, warranty certificates and support evidence.

Who uses it. All roles with document permission.

Before you begin. Use a non-sensitive UAT file with a descriptive name.

Steps. Retest must upload one UAT file, confirm preview, download, search, versioning/expiry where available, generate representative PDFs and inspect every page for clipping, branding, images and QR codes.

Expected result. Files remain tenant-scoped, previews work and downloads match the stored version.

Screenshot. Not captured.

Common problems. Upload success without a registered record, broken image, missing version, PDF clipping and absent logo.

Related features. Projects, inspections, deliveries, support and warranties.

Permissions. Document view/upload/download/version/archive permissions.

Mobile notes. Verify file picker, preview and long filenames.

19. Communications

UAT status: Not Tested

Purpose. Communication actions prepare email or WhatsApp content from a record.

Who uses it. Sales, projects, logistics, support and authorised administrators.

Before you begin. Confirm the recipient and approved test destination. This UAT forbids sending real messages.

Steps. Retest may open, but must not send, communication actions on clients, quotes, invoices, sales, projects, job cards, inspections, deliveries, support, warranties, handovers, suppliers and vendors.

Expected result. The action uses the selected record and does not reveal unauthorised data.

Screenshot. Not captured.

Common problems. Missing action, wrong recipient, stale attachment, unsafe prefilled content and automatic send.

Related features. All operational modules.

Permissions. Communication permission plus access to the source record.

Mobile notes. Verify whether actions open the intended app and can be cancelled.

20. Zoho Integration

UAT status: Partially Passed

Purpose. Zoho Books integration can support catalogue/customer/accounting references while SolarOps retains tenant and workflow ownership.

Who uses it. Tenant administrators and accounting users.

Before you begin. Avoid bulk import/export and never expose tokens. Confirm the selected Zoho organisation.

Steps.

1. In the authenticated Zoho Books session, confirm the organisation is Sorted. 2. Confirm the plan shown is Free. 3. Review only the labelled UAT expense with reference UAT-MANUAL-20260717. 4. Do not edit, import, export, disconnect or expose authentication details. 5. In SolarOps, connection status, organisation mapping, catalogue staging, ProductItem/ProductModel linking, service handling, tax, duplicate prevention and disconnect remain pending because tenant access was blocked.

Expected result. Zoho showed the correct authorised organisation and a single labelled UAT record. SolarOps-side sync behaviour is unverified.

Screenshot.

Screenshot captured: Zoho Books demo expense for Office Supplies with reference UAT-MANUAL-20260717.

Common problems. Wrong organisation, unsafe bulk sync, duplicate ProductItems, incorrect ProductModel link, tax mismatch and token expiry.

Related features. Product catalogue, sales, accounting and company settings.

Permissions. Tenant accounting integration administration.

Mobile notes. Integration administration should be performed on desktop unless specifically verified.

21. Company Settings

UAT status: Blocked

Purpose. Company settings control profile, branding, contacts, currency, tax, documents, inspections, support, warranties, projects, inventory, communications, accounting, payment status, warehouses and users.

Who uses it. Tenant administrators.

Before you begin. Record current values before changing anything. Branding and tax changes affect generated documents.

Steps. Exact settings labels and save behaviour are withheld until tenant access is restored. Retest must open each visible settings page on desktop and mobile, change only a reversible UAT field, save, reopen and restore where required.

Expected result. Settings persist for Sorted only and are reflected in the relevant workflow.

Screenshot. Not captured.

Common problems. Missing settings entry, save without persistence, stale document branding and package-disabled controls.

Related features. Documents, integrations, users, inventory and workflows.

Permissions. Company settings administration.

Mobile notes. Confirm every settings entry is reachable without overflow.

22. Users, Roles and Permissions

UAT status: Blocked

Purpose. Users and roles limit access by job responsibility and protect direct routes.

Who uses it. Tenant administrators.

Before you begin. Do not alter real users unless the original settings can be restored and the owner has approved the test.

Steps. No invitation, deactivation or permission mutation was performed. Retest must use an approved test user to check invitation, activation, deactivation, role assignment, direct routes, tenant isolation, mobile-menu permissions, communication permissions and client access.

Expected result. UI visibility and server-side route protection agree.

Screenshot. Not captured.

Common problems. Hidden menu with accessible direct route, stale session after role change, cross-tenant access and excessive default permissions.

Related features. Account access, navigation and company settings.

Permissions. User/role administration.

Mobile notes. Role-filtered mobile navigation remains unverified.

23. Mobile Field Workspace

UAT status: Not Tested

Purpose. The mobile workspace supports technicians with job cards, deliveries, inspections, scans, photos, files, support visits and signatures.

Who uses it. Field technicians and supervisors.

Before you begin. Use an approved device, network and test records. Grant camera access only when required.

Steps. A 390 x 844 pass was not completed. Retest must cover menu, assigned work, project delivery, inspection, scan, file/photo, support visit, signature, responsive tables, PWA installation and poor-connection messaging.

Expected result. All required controls fit, no content overlaps and interrupted work fails safely.

Screenshot. Required mobile set; not captured.

Common problems. Horizontal overflow, hidden actions, camera persistence, upload loss and no offline warning.

Related features. Job cards, inspections, deliveries, scanning and support.

Permissions. Field role plus module permissions.

Mobile notes. This entire section requires device-size retesting.

24. Client Portal

UAT status: Not Tested

Purpose. The client portal should expose only approved client projects, documents, invoices, warranties, assets, support and handover information.

Who uses it. Invited client users.

Before you begin. Use an approved fictional client account; never use a real client.

Steps. Portal login, dashboard, data visibility and communication were not tested. Retest must verify strict client and tenant scoping, restricted fields and direct-route protection.

Expected result. A client sees only their own approved information.

Screenshot. Not captured.

Common problems. Cross-client visibility, internal notes exposed, missing documents and unrestricted direct routes.

Related features. Clients, projects, documents, warranties and support.

Permissions. Client-portal access and per-record visibility.

Mobile notes. Portal navigation and document viewing need mobile testing.

25. Troubleshooting

UAT status: Guidance based on verified boundaries and required retests

Purpose. Use this section to identify the correct support path without risking data.

Who uses it. All users and tenant administrators.

Before you begin. Record the page, time, company, role and exact message. Do not include passwords, keys, customer data or tokens.

Steps and common problems.

1. Cannot sign in: confirm the correct URL and account; use the approved password-reset flow. Do not share credentials. 2. Incorrect company opens: return to /account; if the company is absent, ask an administrator to review membership. 3. Permission denied or page missing: compare the user role, package entitlement and direct-route result. 4. Upload does not register or image does not display: retain the original file, record format/size and do not repeatedly upload sensitive content. 5. Scanner does not open: check site camera permission. After closing, confirm the camera indicator stops. 6. QR/barcode not recognised: confirm the code type and use the record search as a safe fallback. 7. Search returns no result: use a unique reference; record whether only date filters appear. 8. PDF cut off or logo missing: do not send it; retain the record and attach the PDF to a bug report. 9. Communication action missing: confirm role and package; do not use an external workaround that bypasses logging. 10. Zoho not connected: verify the authorised organisation and integration status; do not paste tokens into support messages. 11. Paystack not configured: contact a billing administrator. Never paste secret keys into SolarOps client-side fields. 12. Subscription feature unavailable: ask SolarOps Support to review the subscription plan, add-ons, temporary access and account status.

Expected result. The issue is documented without destructive retries or secret exposure.

Screenshot. Not applicable.

Related features. Bug register and SolarOps Support troubleshooting.

Permissions. Troubleshooting must not exceed the user’s normal permissions.

Mobile notes. Include device, viewport and network state in mobile reports.

Known Limitations at Version 1.1

- Tenant access and all tenant record-creation workflows require an authenticated Sorted tenant membership or deployed bounded support-access flow. - No tenant MANUAL-UAT - record was created in this pass. - Twelve desktop screenshots were captured. Mobile viewport capture remained blocked by the Chrome control layer. - Fifteen Paystack Test plans were created and verified with zero subscriptions and zero revenue. Checkout and payment events were not executed. - Subscription phase, successful-cycle counting, standard-plan transition and failed-payment access states are implemented and tested in source, but were not migrated or deployed. - Zoho was verified only on the Zoho side; SolarOps-side connection and sync were not tested. - Six Knowledge Base drafts were created and left unpublished. Product image upload was blocked by Chrome extension file-access permission.