Skip to main content
Admin › Settings › General
Set system-wide default behavior — authentication policy, sign-in methods, feature enablement, etc.
  • Changes made here take effect for all users immediately on save.
General settings tab

Manage authentication policy and feature toggles in Admin > Settings > General

​
Authentication Settings

Set policies for user signup, sign-in, and sessions.

​
Default User Role

The role automatically assigned to new sign-ups.
  • Whether a user can use the service right after signup hinges on this value.

​
Authentication Toggles

JWT expiration format: 30m (minutes), 1h (hours), 10d (days), 1w (weeks), -1 (no expiration). -1 is convenient but makes a token hard to revoke if leaked, so in enterprise environments 8h to 1d is recommended.

​
Email De-identification

When the ENABLE_EMAIL_DEIDENTIFY=true environment variable is set, the @ domain part is removed from user email addresses, storing only the ID portion.
Use this when privacy protection requirements dictate not storing full email addresses in DB in SSO/LDAP environments. Same applies to OAuth sign-in users.

​
LDAP Settings

Integrate with corporate LDAP / Active Directory servers for unified authentication.
  • When enabled, an LDAP option appears on the sign-in screen and a form for server connection details expands.
  • When an LDAP user signs in for the first time, an account is auto-created with the Default user role above applied.
LDAP settings apply immediately. Misconfiguration can block user sign-ins, so verify with a test account first.

​
Feature Toggles

Control whether specific features are enabled system-wide.
  • When disabled, the related menus and buttons disappear from the user’s screen and the corresponding API calls are also blocked.

​
Notification URLs

Below the feature toggles, configure the two URLs used for notifications.
  • The three similarly named items below serve different roles.
This is normal when the Default user role is ‘Pending’ (the default). Until an admin approves them, a sign-up only sees the “Account pending approval” screen. Change that user’s role to User in User Management to let them use the service right away. If approving each time is cumbersome, change the Default user role itself to User — but since anyone can then sign up and use the service immediately, only open sign-ups in a trusted environment.
Yes. Even with LDAP enabled, you can sign in with existing local accounts (email/password). When an LDAP user signs in for the first time, an account is auto-created. The default role is the Default user role under “Authentication Settings”.