PlanewardPlaneward Docs
PlanewardPlaneward Docs
Welcome
Community overviewMember access journeySales journeyMoney journeyApps in your communityCommunity notifications

Developers

REST APIAuthenticationWebhooksMCPEmbedded projectsTask description contentDeveloper hub

API

Community

Member access journey

How people sign in to your community (email link or code, Google, Discord, passkeys), how Planeward decides whether they're a member, a team member, a past customer or not in yet, and how buyers confirm their email before they pay.

Your customers have their own sign-in, separate from the Planeward app. It is one buyer account per workspace, used on your community, checkout and account addresses (see Domains and sign-in). Someone signing in only proves who they are: they open an email link, type a 6-digit code, continue with Google or Discord, or use a passkey. Planeward then decides what that person can open. A member is a customer with access to the community. A team member is someone on your workspace team with Community access. A past customer has bought something or has balance history but no community access right now. They can still sign in and land on Settings to manage billing and withdraw their balance. Anyone else is signed in but has no access yet, and is sent to an offer to buy or join. Buyers who aren't signed in confirm their email with a code before they can pay, so every purchase lands on an inbox the buyer really owns.

Related

GuideUse it for
Community overviewHow sales, checkout, access and money fit together
Sales journeyAffiliate links, redirects and how a sale finds its affiliate
Money journeyHow the payment is split, held and withdrawn
Settings → Apps → Community → Sign-inSign-in methods (email link or code, Google, Discord, passkeys, Turnstile) and sign-in page links
Community → Open communityOpen the community as yourself, signed in, in one click
Customers → customer → Community accessSee if a customer can sign in, grant complimentary, suspend

Rule of thumb: Signing in proves an email. Access comes from a purchase (or complimentary access) or from your team. You never create community accounts by hand.


Journey


Ways to sign in

MethodTurned on inWhat the person doesNotes
Magic linkSign-in methods → Email sign-inTypes their email, then clicks Sign in in the emailAlways on unless you pick One-time code. Best opened on the same device.
One-time codeSign-in methods → Email sign-inTypes their email, then types the 6-digit code from the emailWorks when the email is read on another device or in a mail app's browser.
Continue with GoogleSign-in methods → Google (your own OAuth app)Picks their Google accountOnly accepted if Google has verified the email. Matches an existing member by email.
Continue with DiscordSign-in methods → Discord (your own OAuth app)Approves on DiscordRefused if the Discord account has no verified email.
Sign in with a passkeySign-in methods → PasskeysUses Face ID, Touch ID, a PIN or a security keyMembers add one in the Sign-in methods section of Settings in the community. Passkeys are tied to the community's host.
Open community (team)Always available on Community when publishedClicks Open community in PlanewardSigns the team member in on the community straight away. No email.
Send sign-in email (team)Membership row menu, membership page, customer pageA team member with Manage sends a customer a sign-inUses the workspace's email method: a link or a code.

Email sign-in is one choice for the whole community. Emails sent after a purchase or an approval use the same method.

Cloudflare Turnstile is an optional bot check. When it's on, people complete it before a sign-in email or a checkout code is sent. Emails Planeward sends by itself (after a purchase, an approval, or Send sign-in email) skip it.


How Planeward decides who gets in

The same rule answers two questions: "should we email this person a sign-in?" and "what can this session open?". Because both use one rule, a team member is never sent a sign-in that then fails. That was the old login-code bug, where team members needed a complimentary membership to sign in.

  • The team check matches the team member's account email, ignoring case. For Gmail it also accepts dots and + aliases, which always reach the same mailbox. Aliases at other providers aren't accepted: a Yahoo name-keyword address, for example, can belong to someone else. An old invite email doesn't count.
  • A customer with access matches by their email, their primary contact's email or any contact's email. Settings only (below) matches the customer's own email or primary contact's email only, so another contact never sees the customer's billing or balance.
  • One email, several customers: a customer the email owns (its own email or primary contact) comes first. Planeward picks, in order: the oldest owned customer with access, then the oldest customer with access where the email is another contact, then the oldest owned customer with purchase or balance history (Settings only). So someone who bought on their own customer signs in as that customer, not as the company they're also a contact of.
  • Suspend always wins: a suspended member has no access to the community, even with an active plan. They can still sign in to Settings. Their own suspension also wins over a company they're another contact of: they don't get in through the company's access.
Can they…MemberTeam member
Read and post in channelsYesYes, as themselves (team badge)
React, track course progressYesYes, tracked on their team account
Open paid coursesIf their plan unlocks themWith Manage community; team members without it see locks
ModerateNoWith Moderate community (Manage community manages channels)
Settings → BillingEvery subscription they have in the workspace (primary contact only)Hidden: they aren't billed
Settings → BalanceIf they earn revenue share (primary contact only)If their team account earns revenue share
Needs a customer recordYesNo, never

Other contacts of a customer

A customer can have several contacts, like the people at a company. Signing in with any contact's email of a customer with access opens the community: channels, courses and their profile. Billing and Balance belong to the customer's own email or primary contact only. Other contacts don't get the Billing and Balance tabs and can't view receipts, cancel plans, change payout details or withdraw (the server refuses with "Billing and balance are managed by the account's primary contact.").

When another contact buys, the purchase goes on their own customer record (with their email as its primary contact), never on the company's. Once that purchase gives access, they sign in as their own customer, with their own Billing and Balance. If their own plan lapses while the company still has access, they keep the community through the company, and their own billing comes back when that access ends or they buy again. See Who pays.

Past customers: Settings only

A customer with any purchase or balance history can always sign in, by email, Google, Discord or passkey, even without community access. That covers a plan that lapsed or ran its last payment, access you revoked or suspended, and a purchase of a product that doesn't unlock the community. They land on Purchases, in an account view with:

  • Purchases, what they bought, with its downloads and links.
  • Sign-in, to manage passkeys and linked accounts.
  • Balance, only if they have balance history. They can still request withdrawals.
  • Billing, listing every subscription they have in the workspace. They can cancel any of them at any time.

Only the customer's own email or their primary contact's email gets this view. Signing in with another of the customer's contacts shows No access yet.

Suspended members see the same tabs with "Your membership is suspended. You can still view and cancel your plans." They can view billing, receipts and balance, and cancel plans, but can't resume a plan, change payout details or request a withdrawal. They also can't buy or join a waitlist: product pages show "Your membership is suspended. Contact {community name}." instead of the payment options. A payment page opened before the suspension can still be completed, and existing processor subscriptions keep renewing until you cancel them in Stripe or Xendit (or refund the payment).

A few more rules on these tabs, for everyone:

  • Resume only undoes a cancel the member scheduled. A cancel your team set (for example in the Stripe dashboard) has no Resume button; trying to resume it anyway returns "The team set this plan to cancel. Contact them to keep it."
  • Payout QR codes are uploaded as an image on the Balance tab.
  • Payout changes and withdrawal requests are limited to 10 every 10 minutes: "Too many payout changes. Try again in a few minutes."

Profile, channels and courses are hidden. Losing access never signs anyone out: their next page load lands on Settings instead. When they buy again or you restore access, the full community comes back.


Buying: confirm your email first

Every checkout (free, card or bank transfer) needs a confirmed email. A signed-in visitor goes straight to paying. Anyone else confirms with a code on the offer page, which also signs them in.

  • Pay stays disabled until the email is confirmed, with the hint "Confirm your email to continue." Plans, the promo code field (when shown) and payment methods stay visible while they confirm.
  • Nothing is lost on the way: the plan, promo code and affiliate (?a=) stay in the address, and the affiliate is also remembered for 30 days. A buyer who clicks Sign in on the offer comes back to the same offer.
  • People with no access yet who sign in anywhere are taken back to the last offer they opened in that browser. If they never opened one, they see No access yet.
  • Free plans grant access instantly with no second email. Card payments show Activating your access until the payment is confirmed, usually within seconds. Bank transfers wait for your approval, which emails a sign-in. Approving or rejecting a receipt also notifies the buyer; the note you type when rejecting is sent to them (Community notifications).
  • Team members can't check out: "Team members already have access."

Plans with a set number of payments

When a plan has a total number of payments, the checkout summary shows the count and total, like 6 payments · $294.00 total (with any promo code applied), and what happens after the last one:

  • Lifetime access after the 6th payment when the plan keeps access.
  • Access ends after the 6th payment otherwise.

The Stripe and Xendit payment pages say the same: "6 monthly payments in total, then lifetime access." or "6 monthly payments in total, then billing stops and access ends." A buyer continuing an earlier run sees what's left, like "3 more monthly payments, then lifetime access."


What happens on a click

Signing in with email

Buying as a new customer

A team member opens the community


Emails members get

SubjectWhen
Sign in to communityMagic link: someone with access asks to sign in, or after a purchase or approval
code is your community sign-in codeOne-time code: the same moments as above
Your code to confirm your email for communityA buyer confirms their email at checkout
Sign-in after a card paymentAfter Stripe or Xendit confirms a payment, only if the buyer isn't already signed in
Sign-in after approvalWhen you approve a bank receipt, or a waitlist entry is approved (by you or auto-accept on all-free products). Approval unlocks checkout; it gives no access by itself

Every email goes out through your workspace email (SMTP). Links and codes expire after 1 hour.


Protections

ProtectionWhat it does
Rate limits per email5 sign-in emails or checkout codes and 5 code attempts per email every 10 minutes
Rate limits per network30 per IP address every 10 minutes
Checkout code cap200 checkout codes per community per hour
Code rules6 digits, 1 hour, 5 wrong tries, stored scrambled (hashed). A new code replaces the old one.
Sign-in linksOne use, 1 hour
Cloudflare TurnstileOptional bot check before sign-in emails and checkout codes
Own pages onlyCheckout codes can only be requested from your community's own pages
Team emailsNever get checkout codes, so a code can't open a team member's session
No hintsThe sign-in form gives the same answer whether or not an email has access
SessionsLast 30 days. Signing out ends the session. Losing access doesn't: past customers keep their session and see Settings only.

Sign-in page links

On Settings → Apps → Community → Sign-in, under Sign-in page links, add the pages members should see before they continue:

  • Terms of Service, Privacy Policy and Refund Policy: paste each URL. Change the label if your page has another name, like "Community Rules". Leave the URL blank to hide it.
  • More links: up to 5 more, like community guidelines. Each needs a label and a URL.

Every link must be a full https:// address and opens in a new tab. Terms, Privacy and extra links show under the sign-in, join and checkout forms. The Refund Policy shows on checkout only, under the pay button. Members see "By continuing, you agree to the Terms of Service and Privacy Policy." On checkout the Refund Policy joins that line. Extra links show in a row below.


Recommended setup

  1. Set up workspace email first. Settings → Integrations → SMTP, with a transactional sender identity (sign-in emails are transactional). Without it nobody can sign in, and you can't turn on Community or reach its settings, Sign-in methods included.
  2. Pick link or code. Use One-time code if your members often read email on their phone but buy on a computer, or in apps like Gmail that open links in their own browser. Use Magic link if they mostly stay on one device.
  3. Add Google and Discord. One-click sign-in and checkout. In each Configure dialog, copy the Redirect URL into your OAuth app, then paste the Client ID and Client secret.
  4. Set your custom domain before passkeys. Passkeys, the Google and Discord redirect URL and Turnstile hostnames are tied to your sign-in home address, normally your main community domain. Changing it later breaks saved passkeys. There is one redirect URL per provider, whatever other addresses you add.
  5. Turn on Turnstile if you sell. It blocks bots from spamming codes through your email.
  6. Test both sides. Use Open community to check the team view. Open an offer in a private window, confirm an email and buy a free or test plan to check the buyer view.

Staff setup

  1. Go to Settings → Apps → Community → Sign-in. You need Manage community or Manage commerce to change it. View-only teammates see the card read-only. The same settings are on Settings → Apps → Commerce → Sign-in: sign-in is shared by both apps.
  2. Under Sign-in methods, pick Email sign-in: Magic link or One-time code.
  3. Optionally turn on Google or Discord and Configure each one. The badge changes from Not configured to Configured.
  4. Optionally turn on Passkeys, and Configure Cloudflare Turnstile with a Site key and Secret key. Add the hostname shown in the dialog to the Turnstile widget.
  5. Click Save.
  6. Optionally add Sign-in page links (Terms of Service, Privacy Policy, Refund Policy and up to 5 more) and click Save in that section.
  7. To let someone in without a purchase, open the customer and use Community access → Grant complimentary. Use Send sign-in email to email them a sign-in.

Troubleshooting

Nobody receives the email

  • Workspace email (SMTP) isn't set up or has no transactional sender identity. Sign-in emails are transactional, so they need a Transactional & operational (or Shared (legacy)) identity. Set it up in Settings → Integrations → SMTP.
  • The email has no access. The sign-in form sends nothing on purpose and doesn't say why. Check the customer's Community access card: it should show Can sign in.
  • Check spam, then wait a minute: emails are sent in the background.

"No access yet"

The person signed in with an email that has no access and no purchase or balance history. If they paid with a different email, they should click Use a different account and sign in with that one. If they just paid by card, access appears within a minute.

"Confirm your email to continue."

The buyer isn't signed in. They confirm with Send code and Verify email, or Continue with Google / Discord.

"Email confirmation isn't available right now"

The offer doesn't exist any more, workspace email isn't set up, or the community hit its hourly checkout code cap. Fix workspace email, or ask buyers to use Google or Discord meanwhile.

"Too many sign-in requests" / "Too many sign-in attempts"

The per-email or per-network limit was hit. Wait 10 minutes. Each new code replaces the last one.

Passkeys stopped working

The community's main domain changed. Members sign in with email and add a new passkey in the Sign-in methods section of Settings in the community.

Google or Discord says the redirect doesn't match

The Redirect URL in your OAuth app must match the one in the Configure dialog exactly. It changes if your sign-in home address changes.

A team member sees paid courses locked

Their role has View or Moderate but not Manage community. Give their role Manage community to open every course.

A member only sees Settings

They have purchase or balance history but no community access right now: their plan lapsed or ran its last payment, you revoked or suspended them, or they bought a product that doesn't unlock the community. Check the customer's Community access card. Grant access or have them buy a plan to bring back the full community.

A team member has no Billing tab

By design. Team members get in through the workspace and are never billed. Their Balance tab shows if their team account earns revenue share.


Under the hood

For the people building Planeward.

  • The community site runs sign-in: one better-auth instance per sign-in group of addresses (see Domains and sign-in), with Google/Discord, magic link, email codes, passkeys and Turnstile. It stores nothing itself. Every read and write goes to the Planeward app through a remote database adapter, limited to that workspace's own rows.
  • The Planeward app owns the data and decides access. One function, resolveCommunityViewerByEmail, gives the answer: team member first, then a customer the email owns with access, then a customer with access where the email is another contact (skipped when an owned customer is suspended), then an owned customer with purchase or ledger history (Settings only). It is used both before sending an email and when reading a session, which is what keeps sign-in and access consistent.
  • Sign-in tables are separate from Planeward's own users: CustomerAuthUser, CustomerAuthSession, CustomerAuthAccount, CustomerAuthVerification and CustomerAuthPasskey, each scoped to one workspace (the tables keep their old physical names), so a workspace with no community has buyer logins too. A team member's community session never touches their Planeward login.
  • Emails are queued as a sealed (encrypted) Inngest event and sent through the workspace's SMTP. Codes and links never appear in job logs.
  • Rate limits are spent before a code or link is stored, so a limited request never leaves a guessable code behind.
  • Checkout codes have their own path (/community/checkout/verify). It skips the "has access?" rule, because buyers don't have access yet, and checks instead that the offer exists. It still applies Turnstile, the rate limits and the community cap, refuses team emails, and deletes any code that wasn't emailed.
  • Server-started sign-ins (Open community, purchase and approval emails) are signed requests from the Planeward app to the community site. They expire after 60 seconds, can't be replayed and only work on the workspace's own addresses.

Open items

  • Turnstile is optional. Without it, checkout codes rely on the rate limits and the hourly cap. Consider requiring it for communities that sell.
  • Old team "complimentary" customers. Before this change, team members needed a complimentary membership to sign in. Those customer records are no longer needed and could be cleaned up.
  • Team members without Manage and courses. Team members with View or Moderate but not Manage community see paid courses locked. Decide whether View should unlock them.

Community overview

How your community fits together from first click to payout. Your sales page sends buyers to checkout, buyers confirm their email and pay, members get in, and revenue is split, held and withdrawn.

Sales journey

How a visitor gets from an affiliate's link or one of your redirects to your Site sales page, through checkout, and how the sale credits the right affiliate before revenue share splits it.

On this page

JourneyWays to sign inHow Planeward decides who gets inOther contacts of a customerPast customers: Settings onlyBuying: confirm your email firstPlans with a set number of paymentsWhat happens on a clickSigning in with emailBuying as a new customerA team member opens the communityEmails members getProtectionsSign-in page linksRecommended setupStaff setupTroubleshootingNobody receives the email"No access yet""Confirm your email to continue.""Email confirmation isn't available right now""Too many sign-in requests" / "Too many sign-in attempts"Passkeys stopped workingGoogle or Discord says the redirect doesn't matchA team member sees paid courses lockedA member only sees SettingsA team member has no Billing tabUnder the hoodOpen items