# WorkerManager
The WorkerManager manages enrolment and exit of workers for the network. Also it manages their accounts, which, much like user’s accounts, are unique for each pair of worker/token (or worker/SOL). Workers are the operators of the individual nodes that make up the AVS to run Middleware.
Workers are units that carry on computations needed by AVS. To operate it needs stake — this can be either the operator's own funds, which it restakes directly, and assets from other users entrusted to it (delegated). Workers can not manage those funds, they are there as a token of trust from users. If a worker behaves maliciously (e.g. submits bad data or fails his covenant in any other way) thos funds get slashed, partially or fully, depending on severity of the failure.
\
Of course workers can not exit WorkerManager immediately, they should finish all their work and wait for all their stake to be returned, and only after that they can exit the network (AVS). As this process is quite delicate and requires a careful approach - we work through and model different options to choose the best one.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.cambrian.one/cambrian-architecture-and-workflow/workermanager.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.