System Settings & Configuration
Role Required: SUPER_ADMIN / TNCHS_ADMIN
Navigation: Sidebar → Settings
Last Updated: March 2026 | Portal Version: 1.0
Overview
System Settings provides access to platform-wide configuration options that affect all societies. This includes audit system configuration, fee template management, and operational settings.
Platform Configuration
Audit System
| Setting | Value | Description |
|---|---|---|
| Interceptor | Enabled | Automatic audit capture via [Auditable] attribute |
| Archive After | 90 days | Entries archived for compliance |
| Purge After | 365 days | Permanent deletion of old entries |
| Retention Job | Daily 2:00 AM UTC | Automated archival/purge schedule |
Manage audit settings via Audit Logs → Configuration. See Audit & Activity Logs for details.
Society Defaults
When a new society is created, it automatically receives:
- Refund Settings — default cancellation/refund policies
- Agreement Settings — default agreement generation mode
- Fee Configurations — global fee defaults apply until overridden
These defaults can be overridden by the individual Society Admin for their society.
Fee Template Management
Fee templates are predefined sets of fee configurations. As Super Admin, you can:
- View Templates — see all available templates
- Apply Templates — apply a template to a society to create standard fees
- Clone Fees — copy individual fees between societies
See Global Fee Configuration for detailed instructions.
Maker-Checker Policy
Control whether societies require two-person verification for offline payments:
- Navigate to society detail
- Toggle Maker-Checker Policy
- On: Offline payments need a different admin to verify (recommended)
- Off: The recording admin can also verify
This is managed per-society via Society Management.
Payment Gateway Configuration
Payment gateway settings (SocietyPaymentGatewayConfig) are managed at the society level and are audited as CONFIDENTIAL data. These include:
- Razorpay API keys
- Webhook configuration
- Settlement preferences
Gateway configuration changes are logged with WARNING severity. Ensure changes are authorised before proceeding.
Notification System
The platform sends notifications through multiple channels:
- Email — Transactional emails (payment confirmations, booking updates)
- SMS — OTP delivery, critical alerts
- Push Notifications — Mobile app notifications via Firebase
- In-App — Portal notifications
Notification templates and channel configuration are managed at the system level.
Background Jobs
The platform runs scheduled background tasks:
| Job | Schedule | Purpose |
|---|---|---|
| Audit Retention | Daily 2:00 AM UTC | Archive/purge old audit entries |
| Payment Reminders | Configurable per layout | Send milestone payment reminders |
| Session Cleanup | Periodic | Clear expired sessions |
Database Operations
For data-level operations that aren't exposed in the UI, use the provided SQL scripts in the repository:
| Script | Purpose |
|---|---|
cleanup-duplicate-bookings.sql | Remove duplicate booking records |
fix-user-roles-sequence.sql | Fix role assignment sequences |
phase3-pre-migration-cleanup.sql | Pre-migration data cleanup |
Database scripts should only be run after backup and with development team consultation. They are located in the Scripts/ folder of the project.
Azure Infrastructure
The platform runs on Azure with these key services:
- Azure App Service — API hosting
- Azure SQL Database — Primary data store
- Azure Blob Storage — Document and image storage
- Azure CDN — Static asset delivery
Container setup scripts are available in Scripts/Azure/.
Common Scenarios
"I need to reset the platform for a new financial year"
There is no "reset" function. The platform is designed for continuous operation:
- Archive old data through the audit retention policy
- Update fee configurations with new effective dates
- Close old layouts and create new ones as needed
"A society's payment gateway is not working"
- Check the society's gateway configuration (audited entity)
- Verify API keys are current
- Review recent audit logs for
SocietyPaymentGatewayConfigchanges - Test with a small transaction
"How do I add a new admin role?"
Roles are system-defined and seeded in the database. The current roles are:
- SUPER_ADMIN, TNCHS_ADMIN, STATE_ADMIN, REGIONAL_ADMIN, SOCIETY_ADMIN, ACCOUNTANT, CITIZEN
Adding new roles requires a code change and database migration.
Related Pages
- Global Fee Configuration — Fee template and default management
- Audit & Activity Logs — Audit system configuration
- Society Management — Per-society settings