UAAGI Uno Systems Library

The operations and admin reference for UAAGI Uno — the unified digital platform that runs the day-to-day of the United Asia Automotive Group Inc. family of companies (UAAGI, FOTON Motor Philippines, and partner dealerships).

UAAGI Uno is not a single application. It's a set of Odoo-based business systems, a mobile HR front-end, and a Keycloak-brokered SSO layer that lets a single UAAGI identity move seamlessly between them. This library is the single source of truth for how each system is configured, how they connect, and how people actually use them day-to-day.

🗓 Last updated: 2026-04-18 · What's new

The systems

System	Purpose	Primary audience
BPO CRM (uaagi_crm, Odoo 18)	Call-center lead pipeline — captures inbound leads, qualifies, builds a multi-line quotation with bank financing, then endorses to a dealership.	BPO agents, supervisors, managers
Dealer CRM (uaagi_dealership_app, Odoo 18)	Per-dealer instance — receives endorsed leads from BPO, drives them through quotation → order → delivery → Won/Lost. Each dealership runs its own instance.	Dealership sales staff
The Portal (uaagi_dealership_portal)	SSO-authenticated landing page and system picker. Users log in once and pick the dealership they want to work in.	All users
Keycloak SSO	The identity provider. Brokers OAuth 2.0 + PKCE between the portal and every Odoo instance, and carries dealership-access claims in the token.	System administrators
ONe-HR	HR self-service (file OT / leave / OB, approvals, payslips, attendance, profile). Shipped as a mobile app today; Odoo 17 web app for HR admin is documented separately.	All employees, approvers, HR

How they fit together

                    ┌────────────────────────────────────────────┐
                    │              Keycloak SSO                   │
                    │        (sso.uaagi-uno.com)                  │
                    └──────────┬──────────────┬──────────────────┘
                               │              │
           ┌───────────────────┴────┐    ┌────┴──────────────┐
           │  Dealership Portal     │    │  Odoo 18 systems  │
           │  (system picker)       │    │  (BPO + dealers)  │
           └────────────┬───────────┘    └────┬──────────────┘
                        │                     │
                ┌───────┴────────┐       ┌────┴───────────┐
                │ BPO CRM        │ ───▶  │ Dealer CRM     │
                │ (Odoo 18)      │ ◀───  │ (Odoo 18, per  │
                │                │       │  dealership)   │
                └────────────────┘       └────────────────┘

              ┌──────────────────────────────────────────┐
              │              ONe-HR                       │
              │  ┌─────────────┐      ┌────────────────┐ │
              │  │ Mobile app  │◀────▶│ Odoo 17 HR web │ │
              │  │ (iOS/Android)      │ (HR admin)     │ │
              │  └─────────────┘      └────────────────┘ │
              └──────────────────────────────────────────┘

ONe-HR operates on its own HR backend and its own payroll cycle; it is not gated through the dealership SSO. Everything else — Portal, BPO, and Dealer CRMs — sits behind Keycloak.

Audiences

• End users — BPO agents, supervisors, dealership sales staff, and every UAAGI employee using ONe-HR.
• System administrators — configuring brands, dealerships, SSO realms/clients, and the BPO ↔ dealer JSON-RPC integrations.
• HR / MSD personnel — provisioning employee accounts (ONe-HR access), managing employee master data, and processing payroll from the Odoo 17 HR web app.

Start where your work lives

• BPO side: configure in order — Brands, Dealerships, Vehicle Models, Banks. Day-to-day: Intake → Claim → Work → Quote → endorse.
• Dealer side: wire up the BPO CRM Connection first so the dealer instance can call back to BPO. Day-to-day: Intake → Work.
• SSO / Portal: start from Keycloak SSO — realm setup, clients, protocol mappers, and the Odoo configuration that completes the round trip.
• HR / employee-facing: ONe-HR Mobile App for the day-to-day HR experience.