Setting up Accounts for your business
Start by opening **Sites**, selecting the website you want to use and opening its **Accounts** tab. You'll need permission to edit the site. ### Enable Accounts and choose how customers join Under **Account settings**, set **Accounts** to **Enabled**. Choose a **Signup** policy. Under **Organisation accounts**, choose whether customers can create shared organisation accounts or whether the site should support individuals only. ### Set the environment and account address Choose **Development** while preparing and checking your setup. Use **Live** for your production customer service. Enter the published HTTPS address in **Account site URL**. This is the address used for your branded account sign-in. Development and live connections are separate. Any connected apps and payment configuration must match the environment you select. Select **Save account settings** to save your changes. ### Add your account pages Expand **Starter pages and migration** and select **Add account starter pages**. The starter pages include: - Overview - Subscriptions - Invoices and payments - Profile - Members - Services - Sign-in These are editable pages. You can change their names, content and order using the Sites editor. Adding them creates draft pages; it does not publish them. ### Account navigation order The **Overview** page is always kept first in the account navigation, regardless of when it was added. When the combined **Invoices and payments** page is enabled, any separate legacy Invoices link is automatically omitted from the navigation to avoid duplication (the existing invoice route and content remain accessible). ### Apply your branding and layout Use the existing Sites branding controls to choose your business identity and logo. The **account sign-in page** uses a centred, email-first layout that inherits your site's configured branding: - Your **site logo** appears above the sign-in form, automatically selecting the light or dark logo variant based on the visitor's device preference. Sites without a configured logo display the site name instead. - Page and site branding take precedence over the underlying provider workspace identity. - Password sign-in, password visibility toggle, password reset, Google sign-in, account creation and the invite-only restriction are all accessible from the same sign-in layout. Under **Account layout**, you can choose the account header or your website header, control whether the site footer appears, and set a **Header name** and **Help and support URL**. The account layout includes navigation designed for account tasks, including account switching and a profile menu. On mobile, the account switcher shows as a compact icon button that opens a full account-name dropdown. Desktop retains the full named control. ### Decide who can access each page Keep your sign-in page public so customers can reach it before signing in. ### Connect services and subscriptions If customers will use a connected app or buy subscriptions, configure the app through **Settings → Developer** or the connected-app controls available from the site's Accounts panel. The registration needs to match your account site and environment. Paid services also need the appropriate merchant, payment and plan configuration. Connecting your own application may require a developer to complete its sign-in and access integration. Creating account pages alone does not connect an external app. ### Publish account offers and product catalogue Site pricing can be connected directly to customer account subscriptions. From the **Accounts** tab, you can create and manage account offers: - **Free** offers grant access without creating a subscription. - **One-off** offers grant access after verified settlement of a single payment. - **Recurring** offers create subscriptions with monthly, quarterly or annual pricing. Published offers are immutable snapshots. Existing subscriptions keep their agreed prices and terms when offers change or are archived. Display offers on any site page using a **Collection / Pricing** section with its source set to **Account subscriptions**. The section can filter by currency and specific products, and shows a billing toggle for monthly/yearly switching. > **Sandbox note:** End-to-end purchase flows require sandbox verification and a scoped deployment before going live. The catalogue editor is available now, but the full purchase flow must be confirmed with your Hub administrator before opening to customers. ### Plan selection and purchase flow When customers select or change a plan, they are taken through a **Choose and confirm** journey: 1. **Compare options** — customers review available plans side by side. 2. **Review pricing** — a server-generated preview shows the exact pricing, eligibility and trial details for the selected plan. The customer can go **Back** to change their choice without losing the selection. 3. **Confirm** — the customer confirms the reviewed offer. The confirmation uses the same offer revision that was shown in the review step, so prices cannot change between review and confirmation. 4. **Result** — the outcome (success, pending payment, or error) is shown clearly. Failed confirmations keep the draft so the customer can retry with the same command ID. Payment-authentication redirects (such as 3D Secure) restore a fresh authoritative review on return — trial consent is not inferred from the redirect alone. ### Updating a payment method Customers updating a payment method from an offer or trial-renewal review use a **Review and update** focused dialog. The original offer review is retained on cancel or save, so customers do not lose their place in the purchase flow. After a Stripe redirect, a fresh authoritative review is shown without automatically confirming a purchase or renewal. Stripe Elements, connected-account scope and server-side SetupIntent validation remain in place. Setup failures show a **Retry** option. Submission is locked while saving. ### Native Hub catalogue trials Hub catalogue offers support no-card free trials. During a trial: - Metered AI overage is kept unavailable to prevent unexpected charges entering the initial invoice. - The trial end is scheduled at the agreed deadline. A customer with a saved card does not lose their no-card trial unless they explicitly confirm paid renewal. - A confirmed paid purchase after trial expiry requires settlement and grants no further trial. - The customer controls in the account area explain the trial restriction and disable the overage toggle during the trial period. Existing subscriptions retain their accepted trial and billing behaviour. ### Preview and publish Preview your branding, page layout and navigation, then publish through the normal Sites publishing controls. Editor previews disable customer account actions. To check registration, membership and payment behaviour, use your development setup with a separate customer identity before opening the live site to customers.