Authentication — User Guide

Audience: Everyone who signs in to Dagen—email users, Google workspace users, and developers using GitHub SSO.

Overview

Authentication is the gateway to your workspace: RBAC, connections, pipelines, and billing all assume an authenticated identity. The sign-in experience is designed to be readable on first visit and fast for returning users.

Sign-in methods

You can switch between Sign in and Sign up modes from the same screen.

Account creation (email)

1. Open the authentication page.
2. Choose Sign up (or equivalent toggle).
3. Enter email, password, and display name.
4. Submit Create Account.
5. On success you are typically routed to the home / Platform Overview (Platform Dashboard).

Social sign-in (Google / GitHub)

• One-click Continue with Google or Continue with GitHub.
• The provider handles consent; Dagen receives an identity token for session creation.
• GitHub linking may be required again inside Source Repositories if you need repo scopes beyond basic sign-in—follow in-app prompts.

Password field (email accounts)

• Use the eye icon to verify typing.
• Passwords are hashed and stored per security best practices on the server—never commit passwords to repos or paste them into AI Chat.

Session and security

• Sessions persist until logout or expiry (policy depends on deployment).
• RBAC limits admin-only areas such as Team Settings and Model Settings.
• Failed attempts may surface inline errors; social flows may show provider-specific messages.

UX notes (what you see)

The auth screen commonly includes:

• Branded background and centered card with welcome copy that switches between login and signup.
• Loading overlay while a provider round-trip is in flight—avoid double-submitting.
• Clear toggle between “already have an account” and “create one”.

Troubleshooting

Related

• Source Repositories
• Platform Dashboard
• Workspace & sharing (Team Settings)