timvero.comMaven Repository

Initial Configuration

Overview

This guide provides step-by-step instructions for configuring timveroOS after installation. Initial configuration establishes the foundation for your lending operations by setting up core system components and basic workflows.

Pre-Configuration Requirements

Before beginning configuration, ensure you have:

  • System administrator access credentials

  • Organizational structure documentation

  • List of initial users and their roles

  • Basic product requirements defined

  • External system integration details (if applicable)

Core Configuration Steps

1. Organization Structure Setup

Define your organizational hierarchy within the system:

Departments Configuration:

  • Navigate to Settings → Catalogs → Decision Departments

  • Create departments matching your organizational structure

  • Assign department codes and descriptions

  • Set active status for operational departments

Standard Department Examples (from documentation):

  • Underwriting - Credit analysis and risk assessment

  • KYC - Identity and document verification

  • AML - Anti-money laundering compliance

  • Financial - Income and asset verification

2. User Roles and Permissions

Role Configuration Process:

  1. Access Settings → Roles

  2. Create roles aligned with job functions

  3. Assign specific permissions to each role

  4. Map roles to appropriate departments

Key Principles:

  • Implement role-based access control (RBAC)

  • Ensure segregation of duties

  • Configure audit trail requirements

  • Set up approval hierarchies

Initial System Access:

The timveroOS SDK automatically creates a default God Admin user named "admin" during project launch as part of standard RBAC components. Use this account for initial system configuration.

Using the Default Admin Account:

  1. Log in with the default "admin" credentials provided by your development team

  2. Verify access to all administrative menus

  3. Confirm God Admin permissions are active

  4. Keep this account active for initial configuration steps

Critical Requirements:

  • The default "admin" user has full God Admin permissions

  • Use this account to complete initial configuration (steps 1-3)

  • Do NOT create additional users until after notification setup is complete (step 3)

  • Additional users require one-time passwords delivered via notifications

Creating Additional Users:

After completing notification configuration in step 3, you can create additional administrative and operational users:

  1. Navigate to Settings → Users

  2. Click "Create New User"

  3. Enter user details:

    • Full name

    • Email address

    • Username

    • Contact information

  4. Assign appropriate role based on job function

  5. System will send one-time password via configured notification channels

  6. User receives one-time password and can activate their account

Note: Additional user creation is covered in detail after notification setup. The default "admin" account is sufficient for completing initial configuration steps 1-3.

3. Notification Setup

Configure admin-level notification delivery to enable automated communication with applicants, borrowers, and internal teams. This section focuses on administrator configuration tasks, distinct from SDK-level notification event setup completed by your development team.

Overview:

Notification configuration enables timveroOS to send automated messages through email, SMS, and messenger platforms. Proper setup ensures stakeholders receive timely updates throughout the lending process while supporting operational efficiency and compliance requirements.

Important Distinction:

  • SDK Setup (Development team): Creating notification events in code that define when notifications can trigger

  • Admin Setup (This guide): Configuring delivery gateways, creating message templates, and testing notification delivery

Prerequisites Check:

Before configuring notifications, verify that SDK prerequisites are complete:

  1. Check Event Type Availability:

    • Navigate to Admin Panel → Notifications → Templates → Create New

    • Examine the "Event Type" dropdown

    • Verify expected event types appear (e.g., LOAN_APPROVED, PAYMENT_REMINDER)

    • If event types are missing, contact development team

  2. Verify Recipient Types:

    • Check "Recipient Type" dropdown shows required types

    • Standard types: BORROWER, GUARANTOR, AGENT, Organization Employees

For complete SDK prerequisites and verification steps, see Notification Configuration.

Gateway Configuration:

Verify that notification gateways have been configured by your development team at the SDK level. Administrators configure sender presentation details only.

Email Gateway (SMTP):

Prerequisites: Your development team must configure SMTP server connection details (host, port, authentication) at the SDK level before you can use email notifications.

Admin Panel Configuration:

  1. Navigate to Settings → Notifications → Email Gateway

  2. Configure sender presentation:

  3. Test connection to verify SDK configuration is working

Note: SMTP server settings (host, port, connection security, authentication credentials) are configured at the SDK level by your development team, not through the admin panel.

SMS Gateway:

Prerequisites: Your development team must configure SMS provider connection details (API credentials, provider selection) at the SDK level.

Admin Panel Configuration:

  1. Navigate to Settings → Notifications → SMS Gateway

  2. Verify gateway is configured and active

  3. Test SMS sending to confirm SDK configuration

  4. Configure sender display name (if supported by provider)

Note: SMS gateway settings (provider selection, API credentials, authentication) are configured at the SDK level by your development team.

Messenger Gateway:

Prerequisites: Your development team must configure messenger platform connections (API tokens, webhook URLs) at the SDK level.

Admin Panel Configuration:

  1. Navigate to Settings → Notifications → Messenger Gateway

  2. Verify messenger platforms are configured and active

  3. Test message delivery

  4. Configure sender display details (bot name, icon) if applicable

Note: Messenger gateway settings (API tokens, webhook configurations, platform credentials) are configured at the SDK level by your development team.

Initial Template Creation:

Create essential notification templates:

  1. Loan Approval Notification:

    • Event Type: LOAN_APPROVED

    • Recipient: BORROWER

    • Gateway: EMAIL

    • Content: Approval details with loan terms

  2. Document Request:

    • Event Type: DOCUMENT_REQUIRED

    • Recipient: BORROWER

    • Gateway: EMAIL

    • Content: List of required documents with upload instructions

  3. Payment Reminder:

    • Event Type: PAYMENT_REMINDER

    • Recipient: BORROWER

    • Gateway: SMS

    • Content: Payment amount and due date

Testing Notification Templates:

  1. Use "Test" or "Check" button in template editor

  2. Select test entity (application, credit, etc.)

  3. The tool generates a preview showing:

    • How variables populate with actual entity data

    • Final rendered content with all substitutions

    • Conditional logic evaluation

  4. Review the preview to verify correct variable population and formatting

Note: The test function creates a preview of the notification content but does not actually send notifications. To test actual delivery, trigger the notification event in a staging environment or use the notification logs to monitor real event-triggered sends.

Reference:

For comprehensive notification configuration guidance including:

  • Complete SDK prerequisites verification

  • Detailed gateway configuration steps

  • Advanced template creation with variables and conditional logic

  • Troubleshooting delivery issues

  • Integration with workflows and other modules

See Notification Configuration.

4. Initial Product Setup

Create your first credit products:

Product Creation Steps:

  1. Navigate to Settings → Credit Products

  2. Define product parameters:

    • Product name and code

    • Amount ranges

    • Term options

    • Base interest rates

  3. Create at least one additive per product

  4. Configure basic pricing rules

Note: Each product requires at least one additive to be functional.

Reference:

For comprehensive product configuration guidance including:

  • Product architecture and component relationships

  • Additive configuration and pricing rules

  • Product lifecycle management

  • Integration with workflows and underwriting

See Product Architecture and Pricing Configuration.

5. Basic Workflow Configuration

Initial Workflow Setup:

  1. Access the Workflow Designer

  2. Create a simple approval workflow:

    • Add data source connections

    • Define basic decision criteria

    • Set up approval/decline paths

  3. Configure manual review triggers

  4. Test workflow with sample data

Reference:

For comprehensive workflow configuration guidance including:

  • Workflow fundamentals and architecture

  • Decision automation logic

  • Manual review process configuration

  • Workflow vs business process distinctions

See Workflow Fundamentals and Decision Automation.

6. Document Template Creation

Set up essential document templates:

Required Templates:

  • Application forms

  • Approval notifications

  • Decline letters

  • Basic loan agreements

Template Configuration:

  • Use the document designer interface

  • Add merge fields for dynamic data

  • Configure document layout and formatting

Note: Document generation triggers and storage locations are configured at the SDK level by your development team, not through the admin panel.

For detailed document template configuration guidance, see Document Management.

7. Launchpad Configuration

Setup Steps:

  1. Map warning types to departments

  2. Configure assignment rules

  3. Set up review forms

  4. Define escalation procedures

Reference:

For comprehensive Launchpad configuration guidance including:

  • Work queue setup and management

  • Warning type mapping and routing

  • Assignment rules and escalation logic

  • Review form configuration

  • Integration with workflows and notifications

See Launchpad.

8. Initial Testing

Before going live, validate your configuration:

Testing Checklist:

  • Verify default "admin" account has full God Admin access

  • Test additional user accounts and role-based permissions

  • Confirm user one-time password delivery via notifications

  • Create test applications

  • Verify workflow execution

  • Check document generation

  • Validate notification delivery through all configured gateways

  • Test notification template rendering with actual data

  • Confirm email, SMS, and messenger notifications send correctly

  • Confirm data integration (if configured)

Configuration Sequence

Follow this recommended sequence for optimal results:

  1. Foundation: Organization structure and roles (using default "admin" account)

  2. Notifications: Gateway verification and essential templates

  3. Additional Users: Create users who will receive one-time passwords via notifications

  4. Products: Basic product and pricing setup

  5. Workflows: Simple decision logic

  6. Documents: Essential templates

  7. Operations: Launchpad and queues

  8. Testing: End-to-end validation including user access and notification delivery

Note: The default "admin" user with God Admin permissions is created automatically by the SDK during project launch. Use this account for initial configuration steps 1-2.

Common Configuration Considerations

Naming Conventions

Establish consistent naming patterns:

  • Products: Clear, descriptive names

  • Workflows: Include version and date

  • Roles: Department and function based

  • Documents: Type and version indicated

Change Management

Document all configuration decisions:

  • Record configuration choices

  • Note business rationale

  • Track change history

  • Maintain configuration inventory

Testing Approach

Validate configurations systematically:

  • Test individual components first

  • Perform integration testing

  • Include edge case scenarios

  • Document test results

Next Steps

After completing initial configuration:

  1. Expand Products: Add additional products and additives

  2. Enhance Workflows: Build more complex decision logic

  3. Integrate Systems: Connect external data sources

  4. Configure Analytics: Set up dashboards and reports

  5. Optimize Operations: Refine based on usage patterns

Additional Resources

For detailed configuration guidance:

  • Consult the specific module documentation

  • Contact your implementation team

  • Reference the user guides

  • Utilize sandbox environment for testing

This guide covers essential initial configuration steps. For advanced configuration options, refer to the relevant module documentation.

PreviousSystem ArchitectureNextCore Configuration

Last updated

Was this helpful?