Members areas and product access
AI-designed member areas with verified sign-in and private per-product content.
Add a members area
Open your project, then Add members. Choose a name and URL prefix such as /members/. The area has its own page-builder design, revisions and publishing controls. Design it through AI like a website; use an empty section with id="buildasite-members-content" for the managed library. One area is available per project and does not use its funnel allowance.
Products and private content
Open Members area in the project sidebar. Add each product, enter its private text, choose a connected Stripe, Whop or Shopify offer and set an optional number of access days. Without a purchase rule, access is granted manually. Private content is stored separately from generated source and is sent only after a server entitlement check. Do not place private lessons in generated source, public media or external download links.
Purchases and member sign-in
An existing signed, account-verified purchase webhook must match the published checkout placement and its offer. When it supplies a purchaser email, the matching project product receives access. Missing purchaser identity grants nothing automatically. Members sign in with that email and an eight-digit emailed code, expiring in ten minutes and limited to five attempts. Sessions last up to seven days, but product activity, expiry, area status and grants are rechecked on every request. Members do not receive workspace accounts or permissions.
Change access
Grant or revoke products per email in Member access. One member can own several products; another can own a different set. Pausing a product or area blocks delivery immediately. Access days are measured from the grant/purchase. Until-revoked access is a purchase grant, not automatic subscription-status synchronization; refunded or cancelled access should be revoked explicitly in this release. Private text content is supported; public media URLs are not a secure private download mechanism.
MCP and API
Use create_members_area, get_member_area and manage_member_area with a workspace-wide authorized connection. Project administration is required. manage_member_area accepts product, grant, revoke or settings with a payload; private product text belongs in product content, never submit_source. Use the normal child source/editor, preview and publishing tools for the design. Obtain user authorization before changing a member’s access. Customer codes, session tokens and raw provider credentials are never exposed through these tools.