System Configuration

Overview

LAMS system configuration controls how the application behaves in different environments, how documents are stored, how email is sent, and various operational limits. This page is intended for system administrators and technical staff.

Most of these settings require access to the server configuration files and should only be changed with guidance from your technical team.

Email Mode

LAMS operates email in one of two modes:

Mode	What happens
Production	Emails are sent to the actual producers, insureds, and staff
Test	All emails are redirected to a developer address — no real recipients receive anything

Caution

Always confirm the email mode before processing a large batch of renewals or sending a broadcast communication. If the system is in Test mode, none of the intended recipients will receive the emails.

Document Storage

Policy documents, endorsements, and PDFs can be stored locally or in cloud storage:

Mode	Where documents are saved
Local	On the server’s filesystem at a configured path
S3	In an AWS S3 bucket (recommended for production)

Contact your technical team to change the storage mode or configure a new S3 bucket.

File Upload Limits

Setting	Default value
Maximum file size	3.5 GB
Maximum request size	5 GB

These limits apply to document uploads within LAMS. If users report upload failures, verify the file is within these limits before investigating further.

Session Timeout

User sessions expire after 8 hours of inactivity. This is a security setting and cannot be changed from the administration UI. Contact your technical team to adjust the session timeout.

Monitoring

LAMS exposes health and diagnostic endpoints for system monitoring:

• Health check — Confirms the application is running
• Metrics — Application performance data
• Thread dump — Useful for diagnosing performance issues

These endpoints are used by operations and monitoring tools. Contact your technical team for the specific URLs and authentication required to access them.

Note

Never store database credentials, API keys, or security secrets in the documentation or share them in email. Use your organization’s secret management tool or contact your technical team for access to production credentials.