What banks can configure vs fixed platform behavior
What banks often configure (subject to contract)
- Role bundles and permission sets mapped to your job families.
- Product labels and stage names that match your credit manual vocabulary.
- Workflow flags that turn on or off specific queues and exception paths (where the product supports toggles).
- Integration switches at the level your IT controls (environments, feature flags agreed with AIS).
What is typically fixed at the platform layer
- Core product safety rules shared across tenants (e.g., baseline authentication flows-high level only here).
- Release cadence for the Decision PRO application shell managed by AIS (unless you operate a dedicated private build-rare; confirm).
Gray areas
Anything touching model execution, data residency, or custom code is not decided on this page-confirm with your AIS account team.
:::tip What this means for you
Bring a single written “configuration intent” document to workshops so AIS can map it to feasible settings without last-minute surprises.
:::