Skip to main content

Overview

User Authentication settings control how end-users can access your deployed application. These settings have two parts:
  1. Sign-Up Settings: Whether new users can create accounts (and related options)
  2. Authentication Methods: How all users (new and existing) can sign in
These settings are separate from project members—project members are invited directly, while user authentication controls both self-service sign-ups and sign-in methods.

Sign-Up Settings

Allow Sign-Ups

When enabled, new users can create accounts on your deployed application. They’ll see a sign-up option and can register using the authentication methods you’ve configured. When disabled:
  • No new users can register
  • Users who previously signed up can still sign in
  • Project members you’ve invited can still sign in
  • Organization members can still access the app
  • You can still configure authentication methods (email/password, Google, etc.)

Email Verification

When required, users must verify their email address before accessing your application. This helps prevent spam accounts and ensures valid contact information.

Default User Role

Choose the role assigned to new users when they sign up:
RoleDescription
UserRegular user access to your application
AdminAdministrative access with elevated privileges
Most applications should use User as the default. Assign Admin only if you want all self-registered users to have administrative access.

Authentication Methods

Email & Password

Traditional authentication where users create an account with their email address and a password. When enabled:
  • Users see email and password fields on the sign-in form
  • A separate sign-up form is available for new users
  • Password requirements are enforced automatically

Social Login

Allow users to sign in using their existing social accounts. Currently supported:
ProviderStatus
GoogleAvailable
FacebookComing soon
LINEComing soon
Social login provides a streamlined experience—users click one button and are authenticated using their existing account.
When only social login is enabled (no email/password), the sign-up and sign-in experience is unified. Users simply click “Continue with Google” whether they have an account or not.

Configuration

To configure user authentication:
  1. Navigate to your project in the Stardeck dashboard
  2. Go to SettingsAuthentication tab
  3. Configure your preferred settings
  4. Click Save Changes
A live preview shows how your sign-in form will appear to users.

Common Configurations

Private Application

For applications where only invited users should have access:
  • Allow Sign-Ups: Disabled
  • Invite specific users as project members with appropriate roles

Public SaaS

For applications where anyone can sign up:
  • Allow Sign-Ups: Enabled
  • Authentication Methods: Email & Password + Google
  • Email Verification: Required
  • Default Role: User

Social-Only Authentication

For a streamlined sign-in experience without passwords:
  • Allow Sign-Ups: Enabled
  • Authentication Methods: Google only
  • Default Role: User
Users will only see “Continue with Google” on the sign-in page.

How It Works

When a user signs up through your deployed application:
  1. They create an account using your configured authentication method(s)
  2. If required, they verify their email address
  3. They’re registered as a project member with your configured default role
  4. They can now sign in to your application
This is different from users you invite directly as project members—invited users already have a Stardeck account and are assigned a specific role when invited.

Security Considerations

  • Email Verification: Enable this for production applications to ensure valid email addresses
  • Default Role: Use the least-privileged role (User) unless you have a specific reason for Admin
  • Social Login: Provides built-in email verification through the provider

Disable Authentication

For specific use cases, you can completely disable authentication per deployment environment. This is useful for sharing preview deployments with stakeholders who need to see the full admin experience without creating an account.

When to Use

Use CaseRecommended Configuration
Admin Flow PreviewsDisable auth for preview deployments so stakeholders can explore the full admin experience
DevelopmentDisable auth for sandbox to speed up testing without login friction
Client DemosDisable auth for preview to let clients explore the application before committing to setup

Configuration

  1. Navigate to your project in the Stardeck dashboard
  2. Go to SettingsAuthentication tab
  3. In the Disable Authentication section, toggle the environments where you want to disable auth:
    • Sandbox: Your development environment
    • Preview: Preview deployments
    • Production: Your live deployment
  4. Click Save Changes
  5. Confirm the redeployment when prompted
Changing these settings triggers an automatic redeployment for the affected environments. For sandbox, the dev server restarts automatically.
When you disable authentication for production, your application becomes completely public. Anyone with the URL can access all features without signing in. Only disable production auth if you intentionally want a fully public application.

Members & Roles

Learn about inviting specific users and managing roles