Sign In and Onboarding

Sign-in options

GetPaidX uses email verification as the main account path. On supported hosts you may also see Google sign-in as a convenience option, but the app still treats email identity as canonical.

What matters from an end-user perspective:

• email is the reliable way to access your account,
• the app may block disposable email addresses,
• the app may reject Gmail address aliases that use + additions,
• some public pages allow anonymous browsing before you sign in.

When sign-in is required

You can read a lot of public content without logging in, but sign-in is required when you want to:

• publish posts,
• edit your profile,
• manage pricing or payouts,
• start protected workspace flows,
• create PATs, webhooks, or custom domains,
• join place flows that depend on your account state.

Provider onboarding imports

GetPaidX also supports specialized onboarding flows for GitHub and Product Hunt.

These flows are meant to accelerate setup when you already have a public presence elsewhere. The setup pages help you import source information, then the app provisions the corresponding starting profile and workspace state.

Use these routes when you want the app to start from an existing public profile rather than a blank setup.

How walkthroughs and docs differ

Use the manual in /docs when you want to understand what a feature means, what each setting does, and how the product is structured.

Use /marketing/walkthroughs when you want a shorter, scenario-style guide that shows one concrete flow from start to finish.