Flight Manager test workspace

Use the separate development sign-in supplied for this workspace. Your live Hub password is not automatically shared with this isolated environment.

1. Create a client and location, then link them to a job with its pilot and aircraft.
2. Review the method and checklist source selected for the operation. Preparation records are saved separately from flight approval.
3. In Preparation templates, AutoSpray can review and assign a risk register, and configure who must complete each execution check, when it is required and what evidence is needed. These rules require accepted source references. The pilot records their site-specific risks, mitigations and unresolved concerns on the job.
4. Attach sample evidence, review aircraft maintenance and select known batteries. Charging cycles remain separate from flight records. Missing records and due inspections prevent submission.
5. Declare whether the job uses a plant protection product. For a product request, AutoSpray reviews the sources, area and price once; a simulated payment can then release that exact test approval.
6. Use the AutoSpray account to review submitted requests across the test organisations. Open Audit & triage to process queued evidence reviews and inspect recorded findings.
7. Try returned requests, new draft revisions and approval conditions. Use a supplied fictional test aircraft for complete approval exercises; the P100 remains blocked by unresolved source requirements.
8. Upload sample guidance documents, test pilot acknowledgements, record actual flight seconds and use Power reports for date-filtered CSV and location-area exports.
9. Record a run and its completion evidence. From preserved request history, choose “View source and job pack” to collect a printable or JSON copy for that exact submitted revision.
10. Use Account settings to narrow what an individual pilot can see or do, and appoint an existing main pilot to take responsibility for maintenance. Universal restrictions apply to every pilot; earlier appointments and maintenance evidence remain in the history.
11. Import a small, licensed resident-population GeoJSON dataset for a selected planning area. Keep its source references and review any gaps or unknown counts.

Use fictional data. Test approvals do not authorise flight. Permit pricing and simulated payments are available for registered fictional aircraft. No real card payment is taken. Email and push delivery, Hub sharing, scheduled audits and operational dispatch/closeout are still being connected. AutoSpray can inspect separate flight and audit notification records. Delivery is disabled. The audit console supports manual test runs; its findings do not certify compliance. Supporting files can be attached to saved maintenance records. Component records are available for testing; manufacturer policy values require the correct source documents. Planning sources are entered manually. Power reports include all retained geometry versions and immutable submitted areas, with source references and date filters. Repeated revisions are separate records, not a total of unique treated hectares. Later payment observations preserve refunds separately from the original payment receipt. No live Stripe payment is collected.