The Approval Configurator is the application used to define multiple approval levels based on business-rule definitions. Part of the GRC approver framework, it lets an administrator build configurations in which conditions determine which approvers are required and at what level, so that approval requirements adapt to attributes of the record being approved, for example its risk rating or its financial impact.
The alternative names are not delivered applications. A Risk Approver Configuration, an Approver Levels module and a TPRM Approvals module sound plausible, but approvals in this context are not managed by a dedicated third-party risk approvals application; the shared configurator serves that purpose across GRC products.
The use of business rule definitions is what distinguishes this from a fixed approval chain. Rather than hard-coding approvers into workflows, the administrator expresses conditions and levels declaratively, which makes the arrangement maintainable as organizational structure changes. In Third-party Risk Management this supports governance of issue acceptance, exceptions and similar decisions that warrant escalating scrutiny.
When implementing, define approver groups first, then create the configuration with its levels and conditions, and test with sample records to confirm the right approvers are invoked at each level.
[Reference: Study Guide – Other Application Relationships: Approval Configuration and Business-Rule Definitions., ]