Overview
User Authentication settings control how end-users can access your deployed application. These settings have two parts:- Sign-Up Settings: Whether new users can create accounts (and related options)
- Authentication Methods: How all users (new and existing) can sign in
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:| Role | Description |
|---|---|
| User | Regular user access to your application |
| Admin | Administrative access with elevated privileges |
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:| Provider | Status |
|---|---|
| Available | |
| Coming soon | |
| LINE | Coming soon |
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:- Navigate to your project in the Stardeck dashboard
- Go to Settings → Authentication tab
- Configure your preferred settings
- Click Save Changes
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
How It Works
When a user signs up through your deployed application:- They create an account using your configured authentication method(s)
- If required, they verify their email address
- They’re registered as a project member with your configured default role
- They can now sign in to your application
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 Case | Recommended Configuration |
|---|---|
| Admin Flow Previews | Disable auth for preview deployments so stakeholders can explore the full admin experience |
| Development | Disable auth for sandbox to speed up testing without login friction |
| Client Demos | Disable auth for preview to let clients explore the application before committing to setup |
Configuration
- Navigate to your project in the Stardeck dashboard
- Go to Settings → Authentication tab
- 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
- Click Save Changes
- Confirm the redeployment when prompted
Changing these settings triggers an automatic redeployment for the affected environments. For
sandbox, the dev server restarts automatically.
Members & Roles
Learn about inviting specific users and managing roles