This article provides a reference for built-in URLs on your app domain that members and guests use. These routes are reserved by the platform and cannot be used as custom page slugs in the Page Builder. Admins can utilize these links when linking from emails, social posts, navigation, and marketing campaigns.

The canonical sign-in URL for bookmarks, email links, and server auth guards.

Members can also sign in from the header, locked-content prompts, and the auth modal without visiting /login directly.

This URL allows free account registration — email and password, optional name. No payment and no access levels are granted.

A standalone password reset page for email links and direct navigation. Uses the same form content as the auth modal's forgot-password view.

This link allows one-time sign-in from email (magic link or password reset). It is not meant for manual linking and is generated by the system in transactional emails.

The member account hub. Common paths include:

Upgrade modals and billing CTAs link here when a member already has a subscription.

This is the primary member-facing offers page on your app domain.

Query params:

Example: /upgrade?returnUrl=/recipe/summer-salad&accessLevels=uuid1,uuid2

Do not share memberkitchens.com/pricing with your members; share https://yourdomain.com/upgrade or a checkout link instead.

This is a shareable checkout entry point. Each offer can have one or more checkout links; the first is auto-created when you add an offer (slug derived from the offer name, for example /c/monthly-plan).

Manage links in App Station > Monetization > Offers > Checkout Links.

This link initiates the gift purchase flow — buy an offer for someone else. Only available when gifting is enabled for your app (App Station > Monetization > Gifting). Same offer catalog rules as /upgrade (unlisted offers hidden from the gift page).

See Gifting System for more details.

This is a platform compatibility route. If a checkout link has a legacy slug configured, /buy/{code} 301-redirects to /c/{slug}. Configure legacy mappings under App Station > Monetization > Offers > Legacy Links.

These are built-in member routes. Some have admin settings under App Station > Site Structure > List Pages > System Pages.

Custom pages you create in the Page Builder use your chosen slugs (for example /recipes, /meal-plans, /about-us) and are not listed here.

Each content type has a fixed URL pattern:

Locked content teasers and upgrade modals pass returnUrl pointing at these paths so members return after signing in or purchasing.

You cannot create a custom page with any of these slugs — they conflict with platform routes:

account, app-install, c, community, contact, forum, gift, join, leaderboard, login, meal-plan, my-favorites, my-stuff, notifications, points, post, profile, recipe, resource, signup, upgrade, and others reserved for marketing or admin paths on shared hostnames.

The Page Builder shows an error if you try to use a reserved slug. Note that /signup on your tenant domain is reserved for the Member Kitchens creator signup flow, not member registration. Direct members to /join for free accounts.