> ## 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.

# resetApprovalConfiguration

> Clears the stored settings for an approval requirement so the authored defaults apply again.

## 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

Clears the stored settings for an approval requirement so the authored defaults apply again.

Copy method signature

### Returns

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

The configuration with no stored values, at a new revision.

## Route

The method sends `{ expectedRevision, values: {} }` to the update route. Pass `{ expectedRevision, force: true }` instead of the revision number to apply a reset that invalidates open approval cases; the method then adds `force` to the body.

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

> [!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

Read the current revision, then reset the stored settings to the authored defaults.

```ts theme={null}
const { revision } = await para.getApprovalConfiguration(reference);
const restored = await para.resetApprovalConfiguration(reference, revision);
```

## 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 |
| - | - | - |
| 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.