Pre-release Documentation for Ascent Direct Booking. Not yet approved for commercial release. View availability details
Customer records
Accounts, password reset, and the erasure boundary.
The pilot completed a customer password reset from a locally captured link. Partial anonymisation of one ordinary customer exists only on the later unaccepted working tree, not on the frozen 1.2.104 installer.
A customer can finish a password reset from the locally captured reset link.
New pilot result on 1.2.104
The fresh pilot mailed a reset and completed it from the captured key. Login afterwards used the customer account. The request-return address was not rerun.
Before you start. An existing customer account. Local mail is not external delivery.
Limit. The owner does not see the new password. This check is not account erasure and not a change of the login name.
Technical details
Why it matters. Someone who forgets a password can get back in without the owner reading the password.
Example. The customer asks for a reset, opens the latest link, sets a new password, and signs in.
Who uses it. The customer. The account pages.
Status: Cited local evidence. This is not commercial acceptance. Origin: New result recorded on the 1.2.104 local pilot. This guide did not re-run that pilot. Candidate 1.2.104 is not an accepted commercial release. R11 local-pilot ledger, record dated 2026-10-24. This guide did not re-run the pilot. Candidate 1.2.104 is not an accepted commercial release.
The ledger says account claim exists in source. The fresh evidence that passed was the password reset, not a guest-to-account claim walked through in the browser.
Not determined
R14 names account claim and password recovery. The executed fresh step was the reset. Claim remains unresolved as a user-facing demonstration.
Before you start. Unresolved as a completed 1.2.104 demonstration.
Limit. Do not promise that every guest visit becomes an account. Guest booking itself is opt-in.
Technical details
Why it matters. A guest may later need a login. This guide will not describe that handoff as proved.
Example. A guest follows a link to set a password and see the visit. Treat the exact screens as unverified here.
Who uses it. The customer. Account claim, if the installation shows it.
Status: Not determined. Origin: Not determined. Candidate 1.2.104 is not an accepted commercial release. R11 ledger names account claim in source. The executed 2026-10-24 evidence is the password reset. Claim was not separately demonstrated.
Search, contact details, visit history, and ordinary internal notes were not given a fresh 1.2.104 demonstration in the ledger used here.
Not determined
The product contract lists them. The pilot rows used here do not record a directory search or a saved ordinary note.
Before you start. Unresolved.
Limit. Ordinary notes are not clinical notes. This guide does not say who else can read them on 1.2.104.
Technical details
Why it matters. The front desk needs those facts. They stay unresolved rather than being copied from older clinic screens.
Example. The owner looks up a phone number and adds a note that the customer prefers mornings. Unverified on this candidate.
Who uses it. The business owner, and staff only where their role allows. The owner customer area.
Status: Not determined. Origin: Not determined. Candidate 1.2.104 is not an accepted commercial release. Not verified for this guide. Described as unresolved rather than as an available feature.
Partial anonymisation of one ordinary customer was exercised only on the later unaccepted working tree, not on frozen 1.2.104.
Not determined
On that later disposable check, preview wrote nothing and confirmation cleared plugin-owned contact and ordinary notes. The account, login name, visit times, booked prices, and clinical notes remained. No retention period was chosen.
Before you start. Not part of the frozen 1.2.104 evidence.
Limit. This is not complete erasure, not a retention policy, and not a legal certification. Clinical notes and booked prices remained in that later check.
Technical details
Why it matters. A privacy request needs a precise description. The frozen candidate does not have this pass.
Example. The owner previews anonymisation for one synthetic customer and then confirms it. That sequence is not evidence for 1.2.104.
Who uses it. The business owner, on the later working tree only. The later owner control. Not the frozen installer.
Status: Not determined. Origin: Not determined. Candidate 1.2.104 is not an accepted commercial release. Working-tree check after 1.2.104. Not proved on the frozen installer. Not counted as an offered 1.2.104 feature.
A customer account overview is not established. Password recovery on the fresh pilot completed a reset from a captured link. That does not show profile details, visit history, or a page of account settings. Visit history remains unresolved on the customer-directory record.