Module Configuration Guide
Overview
The Go backend uses a configuration-driven module loading system that allows you to selectively enable or disable optional modules. This enables:- Fast startup times in CI/test environments by loading only essential modules
- Environment-specific feature control without code changes
- Fine-grained module management through named profiles and individual overrides
App Profiles
Profiles are named presets that set the initial state of all module flags. Choose a profile based on your deployment needs:full (Default)
Enables all optional modules. Use this in production environments where all features are needed.
Modules enabled:
- Leave Management
- CRM
- Automation
- Bulk Operations
- Export
- Reports
- AI
- Notifications
- Admin
APP_PROFILE entirely—it defaults to full.
smb
Optimized for small-to-medium business (SMB) deployments with all business modules enabled.
Modules enabled: Leave, CRM, Automation, Bulk, Export, Reports, AI, Notifications, Admin
leave
Minimal configuration for leave management-only deployments.
Modules enabled: Leave Management, Admin
core
Minimal configuration with only core functionality. Use in CI/test environments to reduce startup time and resource usage.
Modules enabled: User, Organizations (always-on)
Individual Module Overrides
You can override individual modules on top of any profile usingMODULE_<NAME> environment variables.
Example: Disable AI in SMB Deployment
Example: Enable CRM in Core Profile
Available Modules
Rental Email Configuration
Rental email delivery requiresRENTAL_EMAIL_API_KEY (Resend) and
RENTAL_EMAIL_FROM_ADDRESS. Missing sender credentials fail rental module
initialization rather than silently dropping notices.
Set the rental app origin to its deployed URL so claim emails point to
{RENTAL_APP_BASE_URL}/claim/{token}. Claim secrets are delivered only to the
landlord’s platform email address, never to the partner. Claim emails name the
partner, show the expiry, and include the instruction to ignore the message or
contact support if it was not expected.
Partner notices use exact provider keys: rental:partner-claim:{token_id},
rental:partner-connected:{grant_id}:{connect_request_id}, and
rental:partner-revoked:{grant_id}:{revoked_at} (UTC RFC3339 with fractional
seconds preserved). Unlike existing multi-recipient mails, these single-landlord
keys do not append the recipient ID.
Configuration Precedence
The configuration system applies settings in this order (highest to lowest priority):- Hardcoded — User and Organizations are always enabled
- Individual overrides —
MODULE_<NAME>environment variables - Profile baseline —
APP_PROFILEpreset
Common Deployment Scenarios
Production (Full Features)
Staging (Selective Disable)
CI/Tests (Minimal Startup)
Leave Management Only
Observability
Startup Logging
The server logs module configuration at startup:Health Check Endpoint
The/health endpoint includes per-module status:
- Frontend feature detection
- DevOps tooling verification
- Debugging module initialization issues
Backward Compatibility
IfAPP_PROFILE is not set, the system defaults to full, enabling all modules exactly as they were before this feature. Existing deployments require zero changes.
Environment Variable Reference
Profile Selection
Module Overrides
Configuration File Example
Update your.env file:
Related Documentation
- Architecture Overview:
docs/backend/go/architecture/ - Getting Started:
docs/backend/go/getting-started.mdx - Troubleshooting:
docs/backend/go/guides/troubleshooting.md