Users, roles, and onboarding (high level)
Banks succeed when who does what is clear before software configuration starts. This page describes patterns, not your final org chart.
Typical role families (examples)
| Role family | What they usually do in Decision PRO |
|---|---|
| Relationship / RM | Intake completeness, customer context, handoffs |
| Credit analyst | Assessment, policy checks, recommendations |
| Approver / committee delegate | Decisions within delegated limits |
| Operations | Exceptions, corrections, post-decision tasks |
| Risk oversight | Sampling, challenge, reporting views |
Exact role names and permissions - subject to deployment configuration and your RBAC model (see Security & access).
Onboarding users (no credentials here)
Your bank and AIS typically agree on:
- Identity source - bank SSO vs local accounts (deployment-specific).
- Least privilege - default “view” vs “act” separation.
- Break-glass - who can elevate access and for how long (governance, not product defaults).
- Training - hands-on workshops with sanitized sample data only.
:::caution Never share secrets in documentation
Do not paste passwords, API keys, or private URLs into tickets, email, or wiki pages. Use your bank’s secrets vault and AIS secure channels.
:::
What banks should prepare before go-live
- A role matrix draft (even a spreadsheet) signed by business + risk + IT.
- A pilot branch list and success metrics (time-to-decision, exception rate, etc.).