> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getpara.com/llms.txt
> Use this file to discover all available pages before exploring further.

# updateApprovalConfiguration

> Saves new values for an approval requirement's configurable settings in an authorization scope.

## Import

Call this method on a server-side ParaRestClient created with your server secret key.

```ts theme={null}
import { ParaRestClient } from "@getpara/rest-sdk";
```

async

Saves new values for an approval requirement's configurable settings in an authorization scope.

Copy method signature

### Returns

[`Promise<PermissionsV2AuthorizationConfigurationView>`](/v3/references/types/permissions#permissionsv2authorizationconfigurationview)

The saved values and their new revision.

## Route

Key `values` by the setting `id` the policy declares. Send `0` as `expectedRevision` for the first write.

```text theme={null}
PUT /v1/permissions-v2/authorization-scopes/{authorizationScopeId}/policies/{policyId}/versions/{policyVersion}/requirements/{requirementId}/configuration
```

A `minimum_amount` setting must stay inside the range the requirement declares. Unless the policy sets a `max`, the published threshold is the upper bound, so the setting can lower the threshold but not raise it. A value outside the range fails with `safe_knob_value_invalid`.

> [!NOTE]
>
> An approval case is open while it is `pending`, and after it completes until it is used to sign or expires. Para refuses a change that would invalidate open cases until you confirm it. A confirmed change ends those cases as `invalidated`, and their requests need a new attempt.
>
> Through the API, a refused change returns `409` with code `APPROVAL_CASES_AFFECTED` and the case IDs in `affectedCaseIds`, and nothing changes. To confirm it, send the same change again with `force: true`.
>
> In the REST SDK, the error is a `ParaRestError` with that `code`, and `ParaRestError.affectedCaseIds` lists the cases.

## Example

Use the stored revision, or `0` before the first write, with values keyed by setting ID.

```ts theme={null}
const { configuration } = await para.getEffectiveApprovalConfiguration(reference);
const body = { expectedRevision: configuration?.revision ?? 0, values: { "finance-approvals": 2 } };
const saved = await para.updateApprovalConfiguration(reference, body);
```

## Errors

A non-success response throws `ParaRestError` with the HTTP `status`, the error `code` and a `message`. [Permissions errors](/v3/references/permissions/errors) lists every error code.

An empty path argument throws `ParaRestValidationError` before the request is sent.

| Status | Code | When |
| - | - | - |
| 400 | `INVALID_REQUEST` | A value is not allowed. The message is a validation code such as `safe_knob_not_declared` or `safe_knob_value_invalid`. |
| 403 | `PERMISSIONS_V2_EXTENSION_UNAVAILABLE` | Conditional approvals are not enabled for your API key. Contact Para to enable them. |
| 404 | `NOT_FOUND` | No active requirement matches the reference. |
| 409 | `CONFLICT` | `expectedRevision` is not the current revision. Read the configuration again and retry. |
| 409 | `APPROVAL_CASES_AFFECTED` | The change would invalidate open approval cases. `affectedCaseIds` on the error lists them. Retry with `force: true` to apply the change. |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.