Create and manage a client portal
A client portal gives each client a private, authenticated workspace where they can access shared contracts, invoices, quotes, websites and other records — all connected to your existing Hub objects. ## Create a client portal 1. Open **Sites** in your workspace. 2. Select **New site**. 3. Set **Purpose** to **Client portal**. 4. Give the portal a name, for example *Client portal*. 5. Select **Create site**. New portals start with **invite-only** access and remain unpublished. Add a customer login page, publish the portal through the normal site workflow, then select it on the client's account record before sharing the link. ## Invite a customer Invitations now carry an explicit **Client account** choice, so the customer lands directly in the right account workspace after accepting. 1. Open the portal's **Members** tab. 2. Under **Invite a customer**, enter the customer's email address. 3. Choose the **Client account** (the company whose documents, websites and feedback this customer can access). Leave it blank for contact-only access. 4. Choose a role and select **Create invite**. 5. Copy and share the invite link. If a customer-invite automation is enabled, it may email the invitation automatically. **How acceptance works:** Accepted account-bound invitations open that account's documents, websites and feedback. Contact-only invitations keep their existing destination. Changing the recipient email clears the account choice. The API verifies the account is still active before creating the invite. You can also send record-access invitations from a record's **Access** panel; the same account-binding applies. ## Configure the client workspace on an account For each client account (company, account or contact record), owners and admins configure the portal workspace: 1. Open the account record. 2. Find the **Client workspace** section. 3. Choose the **Customer portal** the client will sign into. 4. If the account record has a **Website** field, it appears automatically as a read-only linked site. 5. Add any additional **Hub websites** explicitly. 6. Add **Quotes** the client should see. 7. Save. The client workspace link never grants access on its own. Every request checks active membership, account audience, site assignment and quote assignment. ## Share quotes with clients Owners and admins can expose published quote snapshots in the client portal: 1. Configure and publish a quote from the **Quotes** list or the quote record. 2. Open the client's account record and select the quote under **Quotes** in the client workspace settings. 3. Save. Clients can view the published offer, accept it, and download the PDF from within their portal workspace. Private drafts are never exposed. Expired published offers remain readable for account history; withdrawn or archived quotes block access. Acceptance requires the client's signed-in email address and a collaborator or higher portal role. ## Show shared records as portal cards Object types can display their shared records as visual cards in the portal instead of a plain list. To enable cards for an object type: 1. Open **Admin → Object types**. 2. Select the object type. 3. Find **Client portal card**. 4. Check **Show shared records as portal cards**. 5. Choose a **Card summary** field. 6. Choose up to **four card fields** to display. 7. Optionally enable **Allow a linked Hub Site on each record** so clients can open the associated published website. 8. Optionally enable **Allow feedback on shared records** to let clients use the record conversation. 9. Save the object type. Cards only appear for records already shared with the client — enabling cards does not share any records. Hidden fields, rich body fields and relationship fields cannot be selected as card copy. **Linked Hub Site on a record:** When the linked-site option is enabled, an owner or admin can select a published sales site on any individual record. Clients see a **View website** button on the card and on the record detail page. Draft sites stay private. To link a site, open the record and use the **Linked Hub Site** section on the Overview tab. ## Use the Website and Delivery library templates The object library includes two templates designed for client delivery work. ### Website template The **Website** object tracks each client website you build or manage: - Set the client account, summary, domain and planned launch date. - Track status: Planning, Building, Client review, Live or Maintenance. - Link the corresponding Hub Site on the record's Overview tab. **Manage site** opens the editor directly. - Link contracts, quotes and invoices for internal management (hidden from the client view by default). - Share the record explicitly when ready. Website uses per-record sharing. Install from **Object types → Object library → Client delivery → Website**. ### Delivery checklist template The **Client delivery bundle** adds a Delivery object and a four-stage pipeline (Confirm scope → Deliver → Review and close → Complete) with eight checklist items covering request, scope, owner/deadline, delivery, evidence, acceptance, billing and next review. Install from **Object types → Object library → Bundles → Client delivery → Install bundle**. Installing the bundle also installs the **Client delivery v1** pipeline. Installing the Delivery object alone does not install the pipeline. **Set up once:** 1. In **Settings → Pipelines**, open **Client delivery v1** and review the stage descriptions and exit criteria. 2. Remove inapplicable requirements or explain why they do not apply. Add any requirements from your own agreements. 3. In the Delivery object editor, adapt the fields and relations to suit your workspace. 4. Decide who owns delivery and who reviews acceptance. **Use for every deliverable:** Each Delivery record tracks one agreed outcome or service cycle, with its own checklist progress and evidence. Use a Website (or another record) for the ongoing relationship, and a separate Delivery for each agreed outcome. Installing this template does not pre-configure client-specific obligations or approve any deliverable. Workspaces adapt the template for retainers, onboarding, maintenance or other services. ## Sites Accounts: a self-service customer account area In addition to the invite-only client portal, Hub Sites can host a **customer account area** through the Sites Accounts feature. This gives your customers: - Self-service sign-in using OIDC and PKCE — no invitation required (depending on signup policy). - Individual or organisation membership, with account switching. - Native subscription and invoice controls through a connected Stripe merchant. - Access to connected-app data and actions through a versioned API and SDK. - Entitlement deliveries with signed tokens and automatic retry. Sites Accounts is separate from the invite-only client portal. It uses a normal Hub Site as the account shell, with the standard site section renderer, builder and publication workflow. > **Activation note:** Sites Accounts requires managed credentials, Firestore indexes, sandbox verification and a scoped deployment before it can serve live customers. The editor and foundation code are available now, but runtime services (sign-in, billing, customer import) remain disabled until an administrator completes the setup steps. See your workspace administrator or the internal setup documentation for activation instructions. ### Set up a customer account site 1. Open a **Sales site** in Hub. 2. Select the **Accounts** tab. 3. Enable Accounts, choose the environment (development or live), set the signup policy and whether organisations are supported. 4. Set the site's canonical HTTPS account URL. 5. Add the editable starter pages (Sign in, Account overview, etc.) to a draft and publish them. 6. Register a connected app in **Settings → Developer** or the site's Accounts panel. Choose the matching site and environment, approved origins and callbacks, merchant, approved prices and features. 7. Complete the activation checklist (managed credentials, sandbox acceptance, collection-group indexes, scoped redeployment). ### Account sign-in The account sign-in page uses a centred, email-first layout that matches Hub's own sign-in experience: - Your **site's configured logo** appears above the sign-in form — the light or dark logo variant is selected automatically from the visitor's resolved system preference. Sites without a configured logo display the site name instead. - Page and site branding take precedence over the underlying provider workspace identity. - Sign-in defaults to **email link** (magic link). A compact text button lets visitors switch to password sign-in while keeping their entered email address. - **Password reset** is available through a small link inside the password field — it opens an email-focused form with a **Send password reset link** action. - Account creation, Google sign-in, and invite-only restriction are all accessible from the same sign-in layout. - Authenticated visitors opening a protected page are redirected directly to the account overview — a second sign-in confirmation step is not shown. ### Account layout and header Account pages use a **compact account header** instead of repeating the website navigation. The compact header contains: - The site's resolved brand (logo and optional editable name, up to 160 characters). - An account switcher — on mobile this is a compact swap-icon button that opens a full account-name dropdown; desktop retains the named control. - Primary page navigation. - A profile menu. On narrow screens, page navigation collapses into a popover. Login pages stay focused and suppress the public header, navigation, footer and promotional widgets. In **Sites → Accounts → Account layout**, owners can: - Retain the website header instead of the compact header. - Opt into the existing site footer. - Set or hide an HTTPS support link. - Add an optional **Header name** (a 160-character label shown in the compact header; blank values fall back to the resolved site branding name without renaming the workspace). ### Account home and services The account home shows a welcoming overview for newly signed-in customers: - A **Welcome to your account** banner. - **Profile and security** shortcuts. - **Services available to you** with compact service cards. Site owners can edit welcome and introduction text, the services heading, the empty-state copy, and which services are shown in the **section inspector**. Free Hub workspace members see their Hub service listed under **Services** without needing a paid subscription. Customers with no active services see a neutral message — the page does not imply that a subscription is required. Customers without an active subscription see an explanation that no services are active and a link to **Explore plans**. Available subscription offers appear under a distinct **Plans available to you** heading. Existing subscribers are directed to their subscriptions without suggesting they need to purchase again. A server-enforced **Anyone signed in** page-access option lets owners publish account layout pages before customer membership exists — starter templates use it for overview, profile and services pages. ### Subscription product catalogue Sites Accounts includes a **subscription product catalogue** (available under **Sites → Accounts**): - **Create or import** membership and add-on products with monthly and yearly prices, optional trial periods and access benefits assigned to connected sites or apps. - **Publish** immutable offers. Existing subscriptions retain their agreed prices and terms when offers change or are archived. - **Display offers** on any site page using the existing Collection / Pricing section with source set to **Account subscriptions**. The section can filter by currency and specific products, and shows a billing toggle for monthly/yearly switching. - **Plan change previews** show all resulting recurring prices — including module bundles and usage meters — before the customer confirms. Previewing a plan never changes a subscription. - **Ended or cancelled subscriptions** show **Next charge: None** and do not display plan-change controls. - Duplicate-purchase protection, payment recovery and server-verified access contributions are built in. - Paused trials can preview and explicitly confirm resumption at their existing agreed price. > **Sandbox note:** End-to-end purchase, plan change, retry, webhook and second-provider acceptance remain pending sandbox verification. The catalogue editor and backend foundations are implemented; the full purchase flow requires deployment and sandbox sign-off before going live. ### Signup policies | Policy | Behaviour | |---|---| | **Open** | Customers can create their own account without an invitation. | | **Request approval** | Customers can request access; an administrator approves membership. | | **Invite only** | Only administrator-issued invitations grant access. | ### Memberships Each customer can have: - An **individual** account (`person_<uid>`) created automatically when they join. - One or more **organisation** accounts, which they create and invite others to. Members have roles within an account: `account_admin` or `account_member`. ## What the client sees From the authenticated client portal, customers can: - View shared quotes, review terms and record acceptance. - Download the quote PDF or an acceptance receipt. - Browse shared records as cards or list items, depending on configuration. - View linked Hub websites and any HTTPS website recorded on their account. - Leave and read feedback through the record conversation. - Access shared contracts, invoices and other documents. All access is callable-only. Disabled members, wrong-account and wrong-site requests are rejected. Viewer and billing roles have read-only feedback access.