Skip to content

The customer panel

Everything a customer can do without opening a support ticket.

1 min read

Customers sign in at /panel. The design goal is that the common questions — what is my key, how do I download, when does this renew, how do I move it to a new domain — are all self-serve.

Dashboard#

Active subscriptions, the newest downloads available to them, and anything that needs attention, such as an expiring update window.

Subscriptions#

One entry per purchase, each showing:

  • The license key, with a copy button.
  • Status and current period end.
  • The update window expiry.
  • Activated domains against the plan’s limit, with add and remove controls.
  • Every version they are entitled to download.

Downloads#

Every entitled version across every subscription, in one list. Releases published after their update window closed are not shown.

Orders#

Purchase history with amounts and dates, and the place a refund is requested from.

Redeem codes#

Visible to customers who arrived through a lifetime-deal marketplace: the codes they have redeemed and the tier those codes add up to.

Referrals#

Their referral link, clicks, signups, conversions, and earnings by status.

Profile#

Name, email, password, interface language, and account deletion.

Getting in for the first time#

A buyer created by a webhook has no password. They get a welcome email with a signed set-password link, and until they use it they are held on that one screen and cannot reach anything else in the panel.

This is the single most common reason a customer reports being unable to sign in after buying — the welcome email did not arrive. Check Email and SMTP before assuming anything else is wrong.

Social sign-in#

Google and GitHub sign-in are available and configurable. A social account matching an existing email links to that account rather than creating a second one.