Domains and sign-in
The three addresses buyers see (community, checkout and account), what happens when you don't set one, and how a customer signs in across them.
Buyers meet your business on up to three addresses. Each one is optional.
| Address | What it serves | Set it in |
|---|---|---|
| Community | The community, and also product pages, checkout and account pages | Settings → Apps → Community → Domain (up to five domains) |
| Checkout | Product pages and checkout links. Account pages too, if there is no account domain | Settings → Apps → Commerce → Domains → Checkout domain |
| Account | Purchases, Billing, Balance and Sign-in | Settings → Apps → Commerce → Domains → Account domain |
Checkout and account domains must be turned on for your server before you can add them. Until then the Domains tab shows a warning, and Planeward answers "Checkout and account domains are not available on this server yet. Use your community domain for checkout until they are turned on." You can have one checkout domain and one account domain once they are. Point each at the CNAME target shown on the page. A domain used for one of these roles can't also be a site's domain.
When you don't set one
Planeward falls back, in this order:
- Account pages use your account domain, else your checkout domain, else your community address.
- Checkout uses your checkout domain, else your community address.
If your community has more than one domain, one is the primary. Product links, emails and the installed app use the primary, and it stays the same when you add another domain.
With Community off, a verified custom checkout domain is required to sell. There is no community address to fall back on. The Ready to sell checklist on Settings → Apps → Commerce tells you.
What each address does when a buyer lands on it
| On the… | Community pages | Checkout pages | Account pages |
|---|---|---|---|
| Community | Served | Served | Served |
| Checkout | Sent to the community (not found if there is none; settings pages go to Purchases) | Served | Served if you have no account domain, otherwise sent to it |
| Account | Sent to the community (not found if there is none; settings pages go to Purchases) | Sent to the checkout address | Served |
Opening the bare address of a checkout or account domain takes the buyer to their Purchases page.
The installed community app stays on the community address. Inside it, links to Billing, Balance, Purchases and product pages stay on that address. Checkout and account domains are for links you send from outside, such as emails, your site and affiliates.
Sign-in across addresses
A customer has one account per workspace, and it works on all of your addresses, whether they are on one domain, on unrelated domains, or include a free platform address.
- Each address keeps its own session. Nothing is shared between addresses behind the scenes.
- One sign-in home. Your workspace has one address where Google, Discord and passkeys run. It is your community's main address, or, with no community, your account or checkout address. Settings → Apps → Commerce → Domains shows Sign-in across your addresses with a Sign-in home badge on it.
- Following a link carries the customer. A signed-in customer who follows one of your links to another of your addresses is carried there already signed in. The link that does it works once and lasts one minute. A customer whose email isn't verified isn't carried and arrives signed out.
- Arriving signed out. On an address that isn't the sign-in home, the customer is checked once against the home before they see the login form.
- Signing out. Signing out on one address signs the customer out of all of your addresses.
Email sign-in works on every address. For Google and Discord:
- One redirect URL per provider. Because those sign-ins run on the sign-in home and bring the customer back to where they started, you register one redirect URL for Google and one for Discord, however many addresses you have. It is shown as Redirect URL in the provider's Configure dialog on Settings → Apps → Commerce → Sign-in (or Community → Sign-in).
- Passkeys are saved on the sign-in home, and customers on your other addresses are sent there and brought back. The notice shows how many are saved. They stop working if the sign-in home address is removed, so choose your main address before customers add passkeys.
Sign-in methods themselves are set in Settings → Apps → Commerce → Sign-in or Community → Sign-in. They are the same setting, and changing them needs the manage permission of every app that is on. See Member access journey.
Removing a domain
On the Domains tab a checkout or account domain has Detach and, in the confirm, Remove. Detach keeps the domain in your workspace so you can use it again. Remove deletes it. The confirm warns you when the domain is the sign-in home or your last checkout domain. Removing a community domain needs Manage community; checkout and account domains need Manage commerce.
Next
Products and what buyers get
A product lists what its buyers get: community access, courses, event tickets, file downloads and external links. Every plan of the product gives all of it, free plans included.
The buyer's account pages
What a customer sees after buying: Purchases, Billing, Balance and Sign-in, and what changes when your workspace has no community.
Planeward Docs