3.O Admin and configuration

Purpose

Every operational lever pulled by business and compliance lives here. The goal: domain users (product, credit, compliance, partner ops) can change product behaviour, policies, pricing, partner setup, and approvals without an engineering deploy for routine changes.

In-scope features

Product configuration

• Product master — name, type (line / term / invoice-backed / etc.), code, status.
• Tenure rules — min, max, allowed values.
• Pricing rules — interest, fees, by risk grade.
• Channel applicability — which channels can sell this product.
• Partner applicability — which co-lending partners support this product.

Policy configuration

• Versioned rule sets — see 3.E.
• Policy editor with sandbox.
• Deployment workflow — propose → review → deploy with effective date.

Pricing and fee

• Pricing grids — risk grade × tenure × channel × partner → rate.
• Fee schedules — processing, servicing, foreclosure, late, bounce.
• GST configuration per fee type.
• Effective dating with audit trail.

Partner / co-lender configuration

• Partner master — see 3.G.
• Partner policy versioned.
• Allocation rules.
• Settlement frequency + escrow setup.

Channel / DSA / CA configuration

• Channel hierarchy — channel → sub-channel → branch → DSA / CA firm → sub-agent.
• DSA payout rules — by product, by ticket, by tenure.
• CA / referral commercial rules.

RBAC

• Roles — application role library.
• Permissions — granular, attached to roles.
• Users with role assignments.
• Tenant scoping for multi-tenant operation.
• Periodic access review workflow.

Branch / team / region

• Org hierarchy.
• Geographical jurisdiction.

Approval matrix

• Per process (sanction, disbursement, deviation, restructuring, write-off, settlement).
• Per ticket-size / risk-grade / channel — different approvers.
• Delegation rules.

Notification templates

• Per event (KFS issued, sanction, disbursement, reminder, bounce, restructuring, etc.) per channel (SMS / WhatsApp / email / IVR) per language.
• Versioned.

Document templates

• Per product, per partner, per language — sanction letter, agreement, DPN, PG, etc.
• Versioned.

Vendor configuration

• Vendor master — see 3.K integration, Section 4.
• API credentials (encrypted secrets).
• Routing rules — primary, secondary, fallback per vendor category.
• Rate limits + circuit breaker config.
• SLA targets per vendor.

Feature flags

• Per environment (dev / staging / prod).
• Per tenant / partner / channel for fine-grained rollout.
• A/B / champion-challenger support.
• Audit log of toggles.

Configuration audit

• Every config change — who, when, before, after.
• Reversion — one-click revert.

Out of scope

• Per-loan operational data — that’s in respective modules.
• Per-borrower data — KYC / application modules.

Key entities

• Product — master.
• Policy — versioned.
• PricingGrid / FeeSchedule — versioned.
• Partner (already in 3.G).
• Channel / Branch / Dsa / Ca.
• Role / Permission / User.
• ApprovalRule.
• NotificationTemplate / DocumentTemplate.
• Vendor / VendorCredential.
• FeatureFlag.
• ConfigAuditEvent.

Key workflows

1. Add new product — config + policy + pricing + fees + templates → review → deploy.
2. Update pricing — propose → review → effective date → deploy.
3. Onboard new partner — config + policy + agreement + integration sandbox → live.
4. Add new role / permission — review by InfoSec → deploy → user assignments.
5. Toggle feature flag — staged rollout per environment / tenant.
6. Vendor swap — change routing rules with traffic-shifting.

Integrations

• Mostly internal — admin UI on top of config services.

APIs

• GET / POST / PUT /admin/products.
• GET / POST / PUT /admin/policies.
• GET / POST / PUT /admin/pricing.
• GET / POST / PUT /admin/partners.
• GET / POST / PUT /admin/roles / permissions / users.
• GET / POST / PUT /admin/approval-rules.
• GET / POST / PUT /admin/notification-templates.
• GET / POST / PUT /admin/document-templates.
• GET / POST / PUT /admin/vendors.
• GET / POST /admin/feature-flags.
• GET /admin/audit-log.

Events emitted

• config.updated (with type and diff)
• policy.deployed
• pricing.updated
• partner.onboarded
• feature_flag.toggled

Edge cases

• Stale configuration in flight — application started under old policy; finished after policy change; record old policy version with application.
• Pricing change mid-day — effective-date controls; in-flight applications hold old price unless explicitly re-priced.
• Permission change for active user — revocation effective immediately; impact on in-progress sessions handled.
• Document template change with backward-compat impact — issued documents reference old version; new uses new.

Compliance touchpoints

• IT MD — access management, periodic review.
• Outsourcing MD — vendor master.
• All product / pricing changes must be board-approved per policy.
• Audit log integrity — protected from tampering.

MVP vs production

Feature	MVP	Production
Product / pricing / fee config	✓	✓
Policy editor	Basic	Full with sandbox
Partner / channel config	✓	✓
RBAC + SSO	✓ (SSO at MVP if internal users)	✓
Approval matrix	✓	✓
Notification / document templates	✓	✓
Vendor master + routing	✓	✓
Feature flags	✓	✓
Multi-tenant config	(Phase 4 — SaaS productisation)	✓

Related: 3.E Underwriting engine, 3.G Co-lending, 3.K Collections, 13.1 Identity access backlog.