Roles, permissions, and navigation
Why your menu may differ from a colleague’s
Decision PRO hides or shows entire areas based on:
- Your role (examples: credit analyst, loan officer, risk manager, compliance officer, administrator).
- Fine-grained permissions (for example, analytics or realtime scoring may require an extra permission even if your role is “risk”).
- Feature flags (some items are labeled Premium or Coming soon in the product-they may be off in your tenant).
You do not need to memorize codes. If you expect an item and do not see it, use Missing menu item? and ask your administrator.
Sidebar groups (typical layout)
These map to Decision-pro/constants.ts (MONITORING_NAV, OPERATIONS_NAV, MANAGEMENT_NAV, ADMIN_NAV):
| Group (plain name) | Typical contents |
|---|---|
| Mission control | Executive dashboard, analytics, system status (admin), audit logs |
| Profiles | Customers (and SME / commercial when available) |
| Intelligence hub | AI center (if enabled), credit scoring, realtime scoring, default prediction, dynamic pricing |
| Loans management | Portfolio, applications, approvals, disbursements, repayments, collections |
| Product factory | Product builder, rules engine, automation (as enabled) |
| Other | vCard, compliance center, integrations, customer service-depending on role |
| Administration | Users, billing, configuration, settings |
Training personas (six buckets)
For classroom design, group the many technical roles into six personas: Platform admin, Credit operations, Risk & portfolio, Modeling / analyst, Compliance, Service / read-only. See the overview in Getting started index and the full enum in repo Decision-pro/types/user.ts for auditors.