Core Configuration
Overview
Core Configuration establishes the foundational technical and compliance settings for the timveroOS platform. Most core configurations are performed at the SDK level during platform implementation, with limited business-level settings available in the Admin Panel.
Admin Panel Configuration
Working Days Calendar
The Working Days Calendar is the primary core configuration available in the Admin Panel, used for SLA calculations, workflow timing, and business day calculations.
Accessing Calendar Configuration:
Navigate to Admin Panel → System → Calendar
Configure working days and holidays
Configuration Options:
Working Days: Select which days of the week are business days (Monday-Friday by default)
Holidays: Add specific dates as non-business days
National holidays
Company-specific holidays
Regional observances
Time Zone: Set default time zone for calendar calculations
Usage:
SLA deadline calculations exclude non-working days
Workflow timers respect business day settings
Notification scheduling considers working day calendar
Example Configuration:
Working Days: Monday, Tuesday, Wednesday, Thursday, Friday
Holidays:
- 2025-01-01: New Year's Day
- 2025-12-25: Christmas Day
- 2025-07-04: Independence Day (if US-based)
SLA Impact:
Application submitted: Friday 5:00 PM
SLA: 24 business hours
Deadline: Tuesday 5:00 PM (skips weekend)SDK Configuration
All other core configuration parameters are managed through SDK-level configuration files and require technical implementation team involvement.
System Parameters
Configuration Method: SDK Configuration Files
Configuration Scope:
System name and instance identifier
Default language and supported language set
Date format conventions
Default currency and supported currencies
Regional settings (country, regulatory jurisdiction)
API base URLs and endpoints
SDK Documentation:
System Configuration - Platform-wide parameters
Localization Settings - Language and regional configuration
Currency Management - Multi-currency support
Note: These configurations are set during platform deployment and require SDK updates to modify.
Branding Configuration
Configuration Method: SDK Configuration Files / Static Assets
Configuration Scope:
Company logo and favicon
Primary and secondary brand colors
Custom CSS styling
Email template branding
Login page customization
Platform title and tagline
SDK Documentation:
Branding Configuration - Visual identity setup
Custom Styling - CSS customization
Asset Management - Logo and image assets
Note: Branding changes require rebuilding and redeploying frontend assets.
Audit Trail and Logging Requirements
Configuration Method: SDK Configuration Files
Audit trail and logging are configured through SDK-level settings during platform implementation.
Configuration Scope:
Event logging granularity (API calls, data changes, user actions)
Log retention periods and archival policies
Audit trail data structure and fields
Integration with external SIEM systems
Compliance reporting requirements
User action tracking scope
SDK Documentation:
Audit Trail Configuration - Event logging setup
Compliance Logging - Regulatory requirements
Log Management - Retention and archival
Note: Audit trail configuration affects storage costs and compliance posture. Consult with compliance and infrastructure teams.
Storage Policies and Retention Requirements
Configuration Method: SDK Configuration Files
Storage policies, data retention periods, and archival strategies are defined through SDK configuration.
Configuration Scope:
Document storage locations (local, cloud storage services)
Data retention periods by document type and entity
Automatic archival triggers and schedules
Storage encryption requirements
Backup frequency and disaster recovery policies
GDPR/data privacy compliance settings (right to erasure, data portability)
SDK Documentation:
Storage Configuration - Storage backends and policies
Retention Policies - Data lifecycle management
Data Archival - Automatic archival processes
Encryption Settings - Data security measures
Note: Storage configuration affects system performance, costs, and regulatory compliance. Changes require careful planning.
Digital Signature Workflows
Configuration Method: SDK Integration
Digital signature functionality requires SDK-level integration with third-party signature providers.
Configuration Scope:
Signature provider integration (DocuSign, Adobe Sign, etc.)
Authentication and API credentials for signature services
Signature workflow templates and routing logic
Certificate management and validation
Signature verification and audit trail integration
Multi-party signing sequences
Document preparation and field mapping
SDK Documentation:
Digital Signatures - Signature workflow integration
Signature Providers - Third-party service configuration
Signature Validation - Document verification
Certificate Management - Signing certificates
Note: Digital signature integration requires contracts with signature service providers and may involve legal review.
Configuration Architecture
Configuration Layers
Understanding where configurations are managed:
Admin Panel Layer
Purpose: Business-user configurable operational settings
Examples:
Working days calendar
User roles and permissions
Workflow designs and business rules
Notification templates
Form builder configurations
Credit product parameters
Department and catalog structures
Access: Business administrators, product managers, operations teams
SDK Layer
Purpose: Technical and infrastructure configurations
Examples:
System parameters (name, language, currency)
Branding and visual identity
Audit trail and logging settings
Storage backend configurations
External system integrations (signature providers, payment gateways)
API authentication and security settings
Database connection parameters
Encryption and compliance settings
Access: Implementation teams, technical administrators, infrastructure engineers
When to Use Which Layer
Use Admin Panel When:
Configuration affects day-to-day business operations
Changes need to be made by non-technical users
Immediate effect without system restart required
Changes are frequent and operational in nature
Configuration is working days calendar
Use SDK Configuration When:
Configuration affects system infrastructure or architecture
Technical knowledge required to understand implications
System restart or redeployment may be necessary
Changes are infrequent and structural in nature
Compliance or security implications exist
External service integrations required
Initial Setup Checklist
Admin Panel Configuration Tasks
SDK Configuration Tasks (Implementation Team)
Implementation Resources
Through the Admin Panel
Working Days Calendar - Business day configuration
User Management - Roles and permissions
Catalogs - System directories and lists
Through the SDK
Platform Configuration - System parameters
Branding Setup - Visual identity
Audit Trail Configuration - Event logging
Storage Configuration - Data storage and retention
Digital Signatures - Signature workflow integration
Security Settings - Encryption and compliance
Related Topics
User Management - Managing users and permissions
Workflow Configuration - Business process setup
Feature Store - External data integrations
For additional support, consult implementation team.
Last updated
Was this helpful?