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

# Configuration

FineParser Enterprise is configured with Helm values. Keep your settings in a values file and pass it to every `helm install` and `helm upgrade`. Helm checks the file against the chart's schema and rejects a mistyped value before anything changes.

## A starting values file

```yaml fineparser-values.yaml theme={null}
serviceAccount:
  create: false
  name: fineparser

storage:
  inProcess:
    efs:
      fileSystemId: fs-0123456789abcdef0
  output:
    s3:
      bucket: my-fineparser-output
  s3:
    region: us-east-2

scaling:
  maxWorkers: 20
```

Apply it:

```bash theme={null}
helm upgrade --install fineparser \
  oci://709825985650.dkr.ecr.us-east-1.amazonaws.com/abbyy/fineparser-enterprise/fineparser-enterprise \
  --version <version> --namespace fineparser -f fineparser-values.yaml
```

## Where settings are documented

| Area | Page |
| - | - |
| Worker pool size | [Scaling](https://docs.abbyy.com/fine-parser/enterprise/concepts/scaling.md) |
| Recognition defaults | [Recognition settings](https://docs.abbyy.com/fine-parser/enterprise/basics/recognition-settings.md) |
| Volumes | [Storage](https://docs.abbyy.com/fine-parser/enterprise/basics/storage.md) |
| Upload limits, exposure, retention | [Production deployment](https://docs.abbyy.com/fine-parser/enterprise/best-practices/production-deployment.md) |
| Node placement | [Node groups and scheduling](https://docs.abbyy.com/fine-parser/enterprise/best-practices/scheduling.md) |
| Every value and its default | [Chart values](https://docs.abbyy.com/fine-parser/enterprise/reference/chart-values.md) |

## Resource names

Resources are named after the release. A release whose name contains `fineparser` uses it as is, and any other name gets `-fineparser` appended. A release named `fineparser` creates `fineparser-ingest`, `fineparser-orchestrator`, and `fineparser-worker`. The examples in these pages use that release in the namespace `fineparser`.

## Applying changes

`helm upgrade` restarts whatever a change affects. Workers finish the unit they hold before they stop, and the orchestrator resumes its queue.

Changing the contents of `worker.userProfile` does not restart the workers. Restart them yourself:

```bash theme={null}
kubectl -n fineparser rollout restart deployment/fineparser-worker
```