For John and Joe / M1 demo / 8 November 2026

Your Magnus walkthrough

Start with the working foundations, then follow Tortoise's staff and customer views. Each stop tells you where to go, what to look for and something useful to try. Keep this guide open beside the app and tick pages off as you go.

Allow about 20-30 minutes for the suggested tour. Choose All pages for the longer route. You can return later and pick up where you left off.

Open the staff demo Go to the tour M1 review checklist

01 / Get ready

Sign in as Tortoise staff

Open the demo, enter the staff email and the password supplied separately, then choose Continue to Magnus. You should land on the Cockpit.

Staff emailowner@tortoise-storage.example.test

Demo address: magnus.hyascent.co. If you reach a different workspace, sign out and check the email you used. If access is unavailable, tell Joe the page and the account used.

02 / Switch sides later

Meet the customer view

Use a separate browser profile or a private window for the customer account. Copy a customer page link into that window so the staff session stays open in your normal window.

Customer emailcustomer@tortoise-storage.example.test

The example customer is Lee Hollowmere, reference TS-0001, with unit G01 at Leyland. Customer pages in this guide are labelled. Passwords and administrator setup details are supplied privately.

What you are reviewing

M1 foundations, with more to explore

M1 foundation

Sign-in, sites, staff, permissions, dashboard, audit and technical foundations.

Extra demo

Units, maps, customer records, bookings, tasks and the customer portal, included early to make the demo useful.

Review with Joe

Technical evidence, programme, business-rule questions and supplier dependencies.

This is a demonstration environment with synthetic records. Billing, card payments, gate control, online identity checks, e-signatures and AI are outside this demo selection. A booking awaiting a missing capability still needs manual confirmation.

The separate Tortoise customer-facing website is not part of this walkthrough. M1's signed requirements stay the same; early previews do not mark later milestones accepted.

The route

Where to go and what to look for

Optional / about 10 minutes more

Three useful things to try

Follow one customer

As staff, search for Hollowmere or TS-0001.
Open the customer record and inspect the linked booking and unit.
In the customer window, compare Storage with that record. You should recognise Leyland and G01.

Customer asks, staff respond

As the customer, open Support and send a request titled John demo review.
As staff, open Support, find the request and reply.
Return to customer Support and check the reply. Keep staff-only notes separate from the customer reply.

Check a boundary

Stay in the customer window.
Enter https://magnus.hyascent.co/operator.
You should see Access unavailable. A customer must not gain staff access.

The support exercise saves records in the shared demo. Use the suggested test title and fictional information. For a read-only tour, inspect the existing request titled Acceptance demo verification 8 November instead. Joe can demonstrate staff permission changes and their audit record with a separate test staff account.

M1 / Review together

Check the foundations

Use these ticks to record what you have reviewed. They are personal notes, separate from formal milestone acceptance. Some requirements are best demonstrated by Joe or supported with evidence outside the app.

F01 / Operator, site and staff set-up
Review both sites, business/contact settings and staff assignments. Ask Joe to demonstrate an invitation using an agreed test account. Platform support access is a separate, recorded administrative process.
F02 / Roles and permissions
Inspect role presets and permissions. Review an allowed staff action, a refused action, and evidence that two operators are separated. The customer-to-staff refusal exercise covers one boundary; it does not replace the staff-role and operator-isolation checks.
F03 / Working dashboard and activity history
Open the Cockpit and Audit. Have Joe make an agreed test setting change and show the actor and time in the activity record. Demo seed entries are sample history, not proof of that review action.
F04 / Technical foundations and recovery evidence
Review responsive navigation, private-file controls, safe errors and background jobs. Ask Joe to show a retained failed job and retry evidence. A populated backup was restored in an isolated environment on 8 November, and the corrected release passed a further backup-based rehearsal. Joe can supply the receipts. Installed-device PWA testing remains separate.
F05 / Programme, rules and supplier dependencies
Review the dated M2-M7 programme, rules and dependency register, data/export list, supplier-request evidence, named owners and open items. Build start is recorded as 19 October. These supporting records need to be supplied or confirmed by Joe; an empty register does not prove supplier requests were sent. Supplier replies and finished integrations are not required for M1.

Evidence already checked for this demo release

On 8 November, the exported build passed local type, lint, boundary, security, build and database checks, including 9,556 unit passes, 1,740 contract passes and 519 database integration passes, with recorded expected failures and skips. The deployed release passed ten database/runtime checks and 30 staff/customer page visits across desktop and phone sizes, including customer refusal from staff pages. These checks support review; they do not claim real-provider operation or production-data acceptance.

Still separate: real customer-data testing, connected provider acceptance, the existing platform owner's hosted MFA journey and installed-device PWA checks. Record any issue against the relevant requirement. This guide is a demo review aid, not a formal submission or final project handover.

Your review

Keep the useful feedback

Notes for Joe

Include the page, the account used, what you tried, what happened and what you expected. Use fictional examples; leave passwords and personal customer details out.

Ticks, filters and notes are saved only in this browser when storage is available. Nothing is sent to Joe automatically. Download your notes before switching browsers or clearing browsing data. Private windows may discard them when closed.