Private access for site and subscription management. Microsoft SSO unlocks directly; password sign-in still requires TOTP before live editing tools open.
Use this for Clean Bean Microsoft admin identities. It unlocks the dashboard directly when the Microsoft account is allowed.
Send a one-click admin sign-in link to an existing Clean Bean admin account. TOTP is still required before the editor unlocks.
If the stored authenticator factor is stale, send a short-lived reset link to this admin email and enrol a fresh TOTP factor.
Saved catalog: Ā·
Create a fresh Stripe Checkout session from the current published billing map and compare the returned line items against the saved catalog prices.
Save here to update the website copy and displayed subscription prices. This step does not change live Stripe checkout billing on its own.
Publish checkout billing separately after saving the display catalog. That step creates or reuses Stripe prices, stores a versioned billing map, and switches checkout to it safely.
Publish the saved catalog into versioned Stripe checkout billing when you are ready. This keeps site copy edits separate from live checkout charges.
Set each postcode area to the early route, later route, or both-window route, then save the draft.
Every postcode area on the reviewed list, plus any manually promoted areas, is shown below with its live route, draft route, and direct route buttons.
Blocks always win over route exceptions. Changes stay as a draft until you use Save update above.
Use a full postcode only when one address needs a different route from its postcode area.
These postcode areas sit outside the fixed reviewed list. Leave them here as reference, or promote one into the main routing board if you need to manage it directly.
Compare the current live rule with the complete result your unsaved draft would give to one full postcode.
Both sides use the same server checker. Running a check does not save the draft or create a booking.
Reference only. These are not part of the normal postcode-area routing list.
Read-only list of subscriptions currently marked active, trial, payment due, or unpaid. Identity, plan, website activity, portal ownership and recorded welcome sends are kept together for a fast operational check.
Each booking below shows the exact Geelus identity, both OptimoRoute orders, both Microsoft Graph calendar events, reminder eligibility/evidence, source timestamp and freshness. Missing, persisted-only and live-validated states are kept distinct.
Click several dates, or Shift-click to select a weekday range. Weekends are already unavailable. Changes appear in the customer calendar immediately.
Records manual or automated cleanup of an ePOS transaction after a cancellation or correction. It is audit evidence, not a normal staff action unless a booking has been changed after reaching ePOS.
Read-only review surface for locker drop-offs. Use the search hooks to load specific submissions by ID, email, phone, or locker number, then inspect the customer content, processing state, and Geelus outcome.
Attach condition or handover images to this locker submission. Files stay private, require strong admin sign-in to view, and are scheduled for retention review after 180 days.
Read-only operator surface for pending, verifying, or send-failed customer email-change requests.
Sends a one-time customer account email through the protected server endpoint. Password reset links take customers to the account screen so they can set their own password.
AAL2-protected case handling for access and deletion requests. Closing a deletion case still requires documented evidence; this queue never performs irreversible deletion by itself.
Read-only lookup against /admin-customer-dsar. Use it to inspect the current case payload, not to trigger raw export packages or irreversible deletion.
Operator surface for /admin-business-accounts. Use it to inspect a parent/child hierarchy, create or promote a parent business account, rename the business record, link a child account, reassign a child, or remove a membership.
Use this when an existing customer profile should become the parent record for a business account. The profile can come from the lookup result or be entered directly.
Moves one existing child record to a different parent profile. This does not merge profiles or rewrite non-business account data.
We use essential cookies and browser storage for site and account features. Reusable booking details are kept with your Clean Bean account, not as an optional profile on this device. Read the privacy details.