Skip to main content
Portal sign-in uses the same Google authentication as the owner dashboard, but the session is scoped to visitor actions — not admin capabilities.

​
When sign-in is prompted

Visitors are prompted to sign in when they try to:
  • Suggest a feature
  • Vote on a feature
  • Post, like, or delete a comment
Browsing the board, roadmap, changelog, and support form does not require sign-in.

​
Auth flow

1

Trigger a protected action

Visitor clicks Suggest, Vote, or Comment without being signed in. A dialog appears with Sign in and Sign up buttons.
2

Authenticate on apex

Bettter redirects to bettter.app/sign-in with a return URL pointing back to the portal page they were on.
3

Session handoff

After authentication, an auth bridge sets the session cookie on the portal host and redirects the visitor back to their original page.
4

Complete the action

The visitor can now suggest, vote, or comment. Sign Out appears in the top-right corner of tab pages.
Sign-in works on both {slug}.bettter.app and verified custom domains.

​
Sign-in dialogs

Buttons: Sign in, Sign up, or dismiss.

​
Sign out

When signed in, visitors see Sign Out in the top-right of portal tab pages (Features, Roadmap, Changelog, Support). Feature detail pages do not show Sign Out in the header.
  • Click Sign Out → shows Signing out… while processing
  • After sign-out, the visitor stays on the same portal page as a guest

​
Portal session vs owner session

Signing in on the portal does not grant dashboard access. Only the project owner can manage content and settings from /dashboard.
The same Google account can be both a portal visitor and a project owner, but each context has separate permissions. Owner actions always require signing in at bettter.app/dashboard.

​
Next

You have completed the documentation. Return to the documentation home or explore the Bettter demo portal to see everything in action.