Page Studio

Agency staff work from a portfolio view protected by explicit Page Studio permissions. Client users see Page Studio inside their existing portal only when a website is assigned to them, and every request remains scoped to that client and membership. Internal provisioning and release controls never leak into the client experience.

The website workspace shows the pages, SEO and form counts from your saved Studio website. Open Studio to edit the same draft, then return to see the latest saved changes. Build a complete page tree with nested subpages, responsive desktop, tablet, and mobile previews, page visibility, shell inheritance, and per-page SEO. Compact preset galleries add canonical sections, page layouts, headers, navigation, mobile menus, footers, themes, and complete site starters as ordinary editable content. AI proposals use the same typed components and controlled operations as manual editing, while revision-safe checkpoints prevent one session from silently overwriting another.

Drafts, editor sessions, checkpoints, reviews, approvals, server-owned builds, and immutable releases are separated so editing does not silently become production. XeroFlow verifies the approved R2 checkpoint and synchronises navigation, footer, theme, SEO, and integrations with the activated release.

The delivery architecture uses Cloudflare Workers and Pages for private build, sandbox, control, and delivery services. Domain registration and custom-domain workflows can be layered into the governed release process as the staged rollout advances, without handing clients unrestricted infrastructure access.

Manage website collections such as services, fleet and testimonials from the agency workspace or client portal once content storage is connected. Editors can maintain descriptions and typed detail fields, while viewers have read-only access. Revision checks protect changes made in another session, and unsaved drafts remain available after a conflict. Saving content prepares a draft; publication still requires a governed release.

The website booking queue lets authorised agency operators review enquiries, save quotes with an expiry date, and record approval, rejection, cancellation and completion decisions. Signed-in business administrators and managers with website editing access can record customer enquiries in their portal and resume the same request after an interrupted response. Each view belongs to the selected website and requires active booking access. Updates check the current booking version, and retries retain the same request so delayed responses do not create duplicate actions. Vehicle reservations, trip confirmation and customer notifications remain separate operational steps during the staged rollout.

Staff can prepare and revise a website setup plan from a starter or brief, review its pages and modules, and keep unconfirmed business details visible before launch. Eligible customer administrators and managers can create a website from a business template or brief. The draft, editor access and initial review proposal are saved together only when subscription limits allow them. Customers with website editing access can submit business details and revised plans from their portal; viewers can read the plan and progress. Agency approval is tied to the current revision. Where the setup service is connected, staff and authorised customer editors can explicitly request preparation of the approved revision and track its progress. Authorised agency staff can record a client’s website access period, permitted modules and limits for sites, pages, storage, domains, AI operations, builds and traffic. Trial access requires an expiry, while client website creation can be enabled separately. Each grant records its reason and actor in the billing audit; matching retries return the original result and competing grants cannot replace existing access. These access grants do not create charges or a paid billing subscription. Renewal, plan changes and provider billing remain separate rollout work.