Overview
System settings provide access to low-level configuration values organized by category. These settings control database connections, authentication, job processing, infrastructure, and AI model behavior. Navigate to Admin > Settings > System Settings.Categories
Settings are organized into tabs by category:
Each tab shows the number of settings in that category.
Viewing Settings
Settings are displayed as key-value pairs with:- Setting name
- Current value (encrypted values are masked)
- Read-only indicator (for settings that cannot be changed from the UI)
Editing Settings
Settings marked as editable can be modified directly from the admin panel. Read-only settings must be changed through environment variables or the Django admin interface.Only settings marked βShow in Dashboardβ in the Django admin are visible here. If you need to access additional settings, use the Django admin interface or configure them via environment variables.
Settings Reference
Legend: Settings prefixed with π store encrypted values. Settings marked
(Dashboard) are visible in the admin dashboard UI. Settings marked (Client) are accessible to the frontend client application.LLM Settings
DB Settings
Graph connectivity usesGRAPH_PROVIDER plus either the Neo4j or FalkorDB connection group.
See Graph backend (Neo4j & FalkorDB) for how switching works and when to run a migration.
Older deployments may still list
USE_NEO4J, USE_FALKOR, FALKOR_DB_USER, or FALKOR_DB_PASSWORD.
Those keys are legacy; GRAPH_PROVIDER with NEO4J_* / FALKOR_* is authoritative for new installs and
the dashboard. Prefer aligning configuration with the rows above.AUTH Settings
Login Methods
ALLOW_PASSWORD_LOGIN, ALLOW_MAGIC_LINK_LOGIN, and ALLOW_SELF_REGISTRATION control which authentication paths the public login/register pages expose. They compose with USE_PROPELAUTH and ALLOW_HYBRID_LOGIN:
- For SSO-only tenants, set
ALLOW_PASSWORD_LOGIN=False,ALLOW_MAGIC_LINK_LOGIN=False,ALLOW_SELF_REGISTRATION=False,USE_PROPELAUTH=True, andALLOW_HYBRID_LOGIN=False. - Magic-link login requires a working email provider (see Transactional Email below). The link is valid for
MAGIC_LINK_TOKEN_TTL_MINUTESminutes.
Transactional Email Deliverability
TheAZURE_ECS_SENDER_ADDRESS, AUTH_FROM_DISPLAY_NAME, and AUTH_REPLY_TO_ADDRESS settings together control how outbound auth emails appear to recipients and to mailbox spam filters:
- The From: line is rendered as
"<AUTH_FROM_DISPLAY_NAME>" <AZURE_ECS_SENDER_ADDRESS>(e.g."Experio" <login@experiolabs.ai>). - A
Reply-Toheader points atAUTH_REPLY_TO_ADDRESSso replies land in a monitored inbox instead of bouncing off the no-reply sender. - Every send also sets
Message-ID(with the senderβs host),Date, andAuto-Submitted: auto-generated, and ships a real plain-text alternative alongside the HTML body β these reduce the chance of the message landing in junk. AZURE_ECS_SENDER_ADDRESSmust be a verified MailFrom on the Azure ECS linked domain. Update it (and the corresponding domain verification) if you re-brand the sender.
SSO / PropelAuth
The five PropelAuth settings (USE_PROPELAUTH, PROPELAUTH_API_KEY, PROPELAUTH_AUTH_URL, PROPELAUTH_SSO_USERS_ACTIVE_BY_DEFAULT, and ALLOW_HYBRID_LOGIN) work together to enable enterprise Single Sign-On. See the SSO Configuration page for complete setup instructions, identity provider guides, and troubleshooting.
Google Workspace Integration
TheGOOGLE_MCP_CLIENT_ID and GOOGLE_MCP_CLIENT_SECRET settings enable per-user Google Workspace MCP integration. See the Integrations page for setup instructions.