> For the complete documentation index, see [llms.txt](https://docs.timvero.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.timvero.com/timveroos-admin-panel-documentation/v.8.2/ops.md).

# Daily Operations (OPS)

## Important: Configuration Dependencies

> **Operations procedures depend on both Building Platform and Admin Panel configuration.**
>
> This documentation provides general guidance for daily operations. The specific screens, fields, options, and workflows you encounter depend on:
>
> 1. **Building Platform (SDK)** — Entity types, states, business processes, and available actions defined by your development team
> 2. **Admin Panel Setup** — Products, workflows, templates, and routing rules configured by your system administrators
>
> **What this means:**
>
> * Your interface may look different from examples shown
> * Available actions depend on your specific configuration
> * Some features described may not be present if not configured
> * Field names and options are customizable per implementation
>
> For configuration changes, contact your system administrator (Admin Panel) or development team (Building Platform).

## Overview

This section covers daily operational tasks performed by lending operations staff using the timveroOS Admin Panel.

## Who Should Read This

| Audience            | Role                                            |
| ------------------- | ----------------------------------------------- |
| **Loan Officers**   | Application processing and customer interaction |
| **Underwriters**    | Manual review and credit decisions              |
| **Servicing Staff** | Loan account management and payments            |
| **Analysts**        | Dashboard and reporting usage                   |

## Working with Entity Actions

Every entity in the Admin Panel displays its available actions as buttons or in a dropdown menu. The dropdown shows **all actions your role permits** — not only those available right now.

Actions are displayed in two states:

| State        | Appearance | Meaning                                                       |
| ------------ | ---------- | ------------------------------------------------------------- |
| **Enabled**  | Black      | Available in the current entity state                         |
| **Disabled** | Grey       | Permitted by your role but not available in the current state |

**Example — Active Credit Product:**

<figure><img src="/files/vUkBYPUoVSbS71eUsxxR" alt=""><figcaption><p>Available at the moment actions are in black and permitted but not available ATM due to the state - grey</p></figcaption></figure>

When viewing an active product, the action dropdown shows:

* **Edit** (grey) — only available when the product is in Draft status
* **Activate** (grey) — not applicable, product is already active

When the product is deactivated, the available actions update automatically to reflect the new state.

This means a grey action is not a permission problem — it is a state problem. If you need to perform a grey action, check what state transition is required first.

> **Note:** Actions that are outside your role permissions entirely do not appear in the dropdown at all. Only actions within your permissions are shown, whether enabled or disabled.

## What's Covered

| Section                                                                         | Purpose                                                 |
| ------------------------------------------------------------------------------- | ------------------------------------------------------- |
| [Origination](/timveroos-admin-panel-documentation/v.8.2/ops/01-origination.md) | Application processing from submission to decision      |
| [Servicing](/timveroos-admin-panel-documentation/v.8.2/ops/02-servicing.md)     | Loan management from disbursement to payoff             |
| [Analytics](/timveroos-admin-panel-documentation/v.8.2/ops/03-analytics.md)     | Using dashboards for origination and servicing analysis |

## Operations by Process

### Origination

Track applications, handle manual decisions via Launchpad, manage participants and documents through the approval process.

**Key Activities:**

* Application status tracking
* Product selection
* Participant and collateral management
* Manual decision handling (Launchpad)
* Document management
* Notification history

[Go to Origination →](/timveroos-admin-panel-documentation/v.8.2/ops/01-origination.md)

### Servicing

Monitor loans, process payments, manage schedule changes, track covenant compliance.

**Key Activities:**

* Loan status tracking
* Payment processing
* Transaction management
* Schedule modifications (restructuring, payment holidays)
* Covenant monitoring

[Go to Servicing →](/timveroos-admin-panel-documentation/v.8.2/ops/02-servicing.md)

### Analytics

Use dashboards to analyze origination pipeline and servicing portfolio performance.

**Key Activities:**

* Viewing embedded dashboards
* Accessing Superset portal
* Analyzing origination and servicing metrics

[Go to Analytics →](/timveroos-admin-panel-documentation/v.8.2/ops/03-analytics.md)

## Related Documentation

* **Configuration**: See [Setup - Platform Configuration](/timveroos-admin-panel-documentation/v.8.2/setup.md) for how to configure features
* **Concepts**: See [Business User Documentation](https://github.com/TimveroOS/timvero-doc-admin-side/blob/main/business_technical_doc/timveroos-business-user-documentation/v.-8.2) for conceptual explanations

***

*For additional support, consult your implementation team.*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.timvero.com/timveroos-admin-panel-documentation/v.8.2/ops.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
