Skip to content
AdlyseDocs
Product guideMCP reference
⌘K
Open Adlyse
⌘K
WelcomeQuick startGlossary

Connect your accounts and bring your team in.

Onboarding wizardAd accountsTeam

The screens you'll check every day.

HomeExplorerReports
Creative intelligence
AI Studio

The context Adlyse works from.

Brand profileFilesTables

Accounts, people, and integrations.

OrganizationIntegrationsAPI keysDeveloper (MCP)
  1. Legacy
  2. Self Hosting

Authentication for Self-Hosting

Configure authentication for your self-hosted Adlyse instance.

Authentication Options#

Email/Password#

Default authentication method. Users register with email and password.

OAuth Providers#

Configure third-party login:

  • Google
  • GitHub
  • Microsoft

SAML/SSO#

Enterprise single sign-on integration.

Configuration#

Email Authentication#

Enabled by default. Configure email settings:

env
EMAIL_HOST=smtp.example.com
EMAIL_PORT=587
EMAIL_USER=your-email@example.com
EMAIL_PASSWORD=your-password

Google OAuth#

env
GOOGLE_CLIENT_ID=your-client-id
GOOGLE_CLIENT_SECRET=your-client-secret

GitHub OAuth#

env
GITHUB_CLIENT_ID=your-client-id
GITHUB_CLIENT_SECRET=your-client-secret

Security Settings#

Password Requirements#

Configure in your environment:

env
PASSWORD_MIN_LENGTH=8
PASSWORD_REQUIRE_UPPERCASE=true
PASSWORD_REQUIRE_NUMBERS=true

Session Configuration#

env
SESSION_TIMEOUT=3600
SESSION_SECURE=true

SAML Integration#

For enterprise SAML/SSO setup, contact us for configuration assistance.

Best Practices#

  1. Enable HTTPS in production
  2. Use strong, unique secrets
  3. Configure proper session timeouts
  4. Enable MFA when available
  5. Regularly audit user access