Global Configuration
Global Settings Guide
The Global Settings interface allows administrators to configure core system settings that affect how the application handles phone numbers, time zones, file uploads, and OTP verification.
These settings apply to all users and modules across the platform, so they should be configured carefully.
Accessing Global Configurations
From the main dashboard:
- Go to Configuration
- Select System
- Click Global Settings
This will open the system-wide configuration page.
Who Can Access This?
Access to Global Configuration is restricted by Role Management.
Only users who have been granted the appropriate permissions under:
Configuration → Role Management
Learn how to assign these permissions.
(Role Permission Link)
Global Settings Overview
The Global Settings interface allows administrators to configure the following options:
- Phone Country Code
- Time Zone
- Phone Number Length
- Maximum File Upload Size
- OTP Attempt Limit
Each setting controls how the system behaves globally.
Phone Country Code
The Phone Country Code defines the default international dialing code used for phone numbers stored in the system.
Steps
- Click the Phone Country Code dropdown.
- Select the country code for your organization.
Example
+94 (Sri Lanka)
Why This Is Important
- Ensures phone numbers follow the correct international format
- Required for SMS notifications and OTP verification
Time Zone
The Time Zone setting determines the default time used for all system operations.
This affects:
- System logs
- Reports
- Notifications
- Workflow schedules
Steps
- Click the Time Zone dropdown.
- Select the correct time zone.
Example
Asia/Colombo
Best Practice
Always select the time zone where your organization primarily operates.
Phone Number Length
This field controls how many digits are allowed for phone numbers entered in the system.
Example
If the length is set to:
9
Valid phone numbers will look like:
771234567
(The country code is not included in this count.)
Why This Matters
- Prevents incorrect phone numbers
- Ensures consistent data formatting
Max File Upload Size (MB)
This setting defines the maximum file size users can upload to the system.
Example
If the value is set to:
100 MB
Users cannot upload files larger than 100 MB.
Common Uses
This applies to files uploaded through:
- Forms
- Attachments
- CRM documents
- Workflow uploads
Best Practice
Choose a value that balances:
- System performance
- User requirements
OTP Attempt Limit
The OTP Attempt Limit defines how many times a user can enter an OTP before verification fails.
Example
If the limit is set to:
4 attempts
The user has 4 chances to enter the correct OTP.
If they exceed the limit:
- OTP verification fails
- The user must request a new OTP
Security Benefit
This helps prevent repeated unauthorized attempts to guess the OTP
OTP Reset Interval (seconds)
The OTP Reset Interval determines how long the system waits before allowing a new OTP request.
Example
180 seconds
Users must wait 3 minutes before requesting another OTP.
Purpose
- Prevents excessive OTP requests
- Protects SMS services from abuse
- Reduces system load
Best Practice
A value between 120 – 300 seconds is recommended.
OTP Attempt Block Time (minutes)
Defines how long a user will be blocked from OTP verification after exceeding the maximum number of allowed attempts.
Example
120 minutes
If a user enters the wrong OTP too many times, they will be blocked for 2 hours before trying again.
Purpose
- Enhances account security
- Prevents repeated brute-force attempts
File Storage Type
Defines the storage system used for uploaded files.
Example
Local
Available Options
| Storage Type | Description |
|---|---|
| Local | Files are stored on the application server |
| Cloud Storage (if enabled) | Files are stored on a cloud storage provider |
Recommendation
- Local Storage → Suitable for small to medium deployments
- Cloud Storage → Recommended for scalable production environments
Saving Changes
After updating the settings:
- Click Save Configuration
- The system will apply the new settings immediately.
Note: Changes will be applied system-wide.
Best Practices
Before changing global settings in a production environment:
- Review the impact on users and inform your team if required
- Always verify the time zone before going live