Pre-release Documentation for Ascent Direct Booking. Not yet approved for commercial release. View availability details
People and access
Invitations, passwords, and removing access without pretending history vanished.
The pilot invited a practitioner, rejected the old invitation link, set a password, and showed that revocation blocks that person’s access. It did not revoke the business owner in that pass.
A service can be limited to the practitioners who are allowed to perform it.
Previously accepted slice, carried forward
Eligibility was part of the accepted 22 October 2026 slice. The 1.2.104 pilot did not repeat the eligibility form.
Before you start. The accepted slice. The later candidate was not accepted as a whole.
Limit. Eligibility is not a qualification check and not a clinical credential. It does not assign a room or an assistant.
Technical details
Why it matters. Customers are not offered a person who does not carry that service.
Example. Two practitioners exist, and only one is ticked for a service. The booking page should offer that person for that service.
Who uses it. The business owner. The service and team editors.
Status: Cited local evidence. This is not commercial acceptance. Origin: Accepted as a local slice, then carried into 1.2.104. Not rerun on the fresh pilot. Candidate 1.2.104 is not an accepted commercial release. M2A local acceptance dated 2026-10-22. The later 1.2.104 candidate contains that slice and is not accepted as a whole. This guide did not re-run the slice.
The owner invites a practitioner, can resend, and the previous link stops working when a new one is issued.
New pilot result on 1.2.104
On the fresh pilot, staff 2 received an invite and a resend. The old link returned 403. The new link set a password and redirected. Resend did not create a second account in the earlier access proof.
Before you start. A practitioner record. Local mail capture is not proof the message left the server.
Limit. The pilot did not revoke staff 1. Invitation mail in the pilot was local capture. This does not create a login for customers.
Technical details
Why it matters. A new person can set their own password. The owner does not choose or read that password.
Example. The owner invites by the practitioner’s name, the person opens the latest email, and sets a password. The first email link no longer works.
Who uses it. The business owner sends the invite. The practitioner sets the password. The team access controls and the invitation link.
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.
Scoped reading. Choosing who may perform a service is practitioner eligibility. This invitation is the separate account-setup message. The fresh pilot captured that message locally, which is not proof it reached an inbox. Practitioner eligibility
Remove access and keep history
Revoking a practitioner blocks that person’s access. The evidence used a staff member who was not the business owner.
New pilot result on 1.2.104
The frozen 1.2.104 revoke proof denied staff 2 in the same session and on a fresh request. The business-owner revocation case was an earlier proof, not this pass. Restoring access did not, by itself, resume that person’s bookings in the earlier proof.
Before you start. A practitioner account other than the protected owner case.
Limit. The 1.2.104 pass did not revoke the owner. Do not describe revocation as deletion of clinical or booking history. Pausing new work and removing login access were distinguished in the earlier proof, not re-run here.
Technical details
Why it matters. Someone who has left can be stopped from signing in without the need to delete past appointments as the access check.
Example. The owner revokes a practitioner. That person’s next request for the staff diary is refused. Old visits remain in the diary the owner can see.
Who uses it. The business owner. Team access.
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.
A practitioner viewing only their own assigned work was not re-checked in the 1.2.104 pilot notes used here.
Not determined
Revocation removed staff-diary scope for the revoked person. A positive own-work browser pass is not in the 1.2.104 rows cited here. Older pilot notes said a therapist could view their own schedule and could not reschedule it themselves.
Before you start. Unresolved on 1.2.104.
Limit. Do not promise self-service reschedule or cancellation by a practitioner. Those were explicitly unavailable in the older pilot note and were not re-opened here.
Technical details
Why it matters. People should see their own day without seeing the whole business. The current pilot write-up does not prove that screen.
Example. A practitioner signs in and expects only their appointments. Treat the exact screen as unverified on this candidate.
Who uses it. The practitioner. The staff diary, if that installation shows it.
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.