# Approval group change approvals

Wallet-as-a-Service (Palisade) now supports approval requirements for changes to approval groups. This adds governance for the controls that decide who can approve sensitive actions such as transactions, policy changes, user management, address book updates, and API credential changes.

Previously, users with permission to manage approval groups could update those groups directly. With approval group change approvals, organizations can require active owners to approve approval group changes before they take effect.

## What's new

### Approval requirements for approval group changes

You can now configure an approval requirement for approval group changes from the existing approval groups experience.

When configured, creating, updating, or deleting an organization-level approval group creates a pending approval request. The requested change is applied only after the required number of active owners approve it.

### Wallet-level approval group overrides

Wallet-level transaction approval group overrides are also covered. If approval group change approvals are configured, changes to a wallet's custom transaction approval group enter the same pending approval flow before they take effect.

### System-managed approvers

Approval group change approvers are based on active organization owners. The approver membership is managed by the system, and organizations configure the approval threshold.

This model helps prevent a single administrator from changing the approval rules that protect high-risk operations without oversight.

### Pending states and notifications

Approval group changes can now appear as pending creation, pending update, or pending deletion. Approvers can review, approve, or reject the requested change in the Wallet-as-a-Service (Palisade) web console.

If the request is rejected or expires, the existing approval group configuration remains unchanged.

## Availability

Existing approval group behavior is unchanged unless approval group change approvals are configured for the organization. Organizations that do not configure this approval requirement can continue managing approval groups as before.