> For the complete documentation index, see [llms.txt](https://platformdocs.lattica.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platformdocs.lattica.ai/architecture-overview/management-client.md).

# Management Client

The Management Client is designed for **Computation Providers** to manage all aspects of computation setup, integration, and resource management. Providers can perform these activities using either the **Lattica Web Console** or the **Python SDK**.

{% hint style="info" %}
Before using either option, you must **sign up** on the Lattica Console to create an account and receive your **Account ID**.
{% endhint %}

{% stepper %}
{% step %}

### Installing the Management Package (Python SDK)

If you choose to use the Python SDK, [install](/how-to-guides/client-installation/how-to-install-management-client.md) the **Management Client package.** This package provides all functionalities needed for deploying computations, managing tokens, and controlling workers.
{% endstep %}

{% step %}

### Model Compilation and Integration

The Management Client enables Workload Providers to deploy and manage their computations in Lattica’s system.

* **Deployment Options**:
  * Use the **Web Console** for an intuitive user interface.
  * Use the **Python SDK** for programmatic integration.
* **Process**:
  * [Deploy](/how-to-guides/workload-lifecycle/how-to-deploy-workload.md) workload to LatticaAI’s backend
  * Workloads can be [managed](/how-to-guides/workload-lifecycle/how-to-modify-workload-settings.md) (updated, activated, or deactivated) after deployment.

{% hint style="warning" %}
**Note**: The model will be ready for processing only after LatticaAI builds the **homomorphic-ready model** in the backend. 

After LatticaAI confirms the model's successful creation, the provider can begin using it for encrypted data processing.
{% endhint %}
{% endstep %}

{% step %}

### Access Token Management

The Management Client provides tools to manage **User Access Tokens**, which control secure access to deployed computations.

* **Token Functions**:
  * [Create ](/how-to-guides/access-control/how-to-create-user-access-token.md)new tokens.
  * [Activate or deactivate](/how-to-guides/access-control/how-to-modify-user-access-token-setting.md) tokens.
  * [Assign ](/how-to-guides/access-control/how-to-assign-token-to-workload.md)or [reassign ](/how-to-guides/access-control/how-to-remove-tokens-assignment.md)tokens to specific workload.

These activities can be performed via the Web Console or the Python SDK.
{% endstep %}

{% step %}

### Worker (GPU) Management

After workloads and tokens are set up, Providers can control computational resources by managing **workers**.

* **Worker Functions**:
  * [Start](/how-to-guides/resource-management/how-to-start-worker.md) or [stop ](/how-to-guides/resource-management/how-to-stop-worker.md)**workers** as needed for active operations.
  * [Monitor ](/how-to-guides/resource-management/how-to-monitor-worker-performance.md)worker performance and optimize resource allocation.

Providers can perform these activities through the Web Console or Python SDK, giving full control over runtime and resources.
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://platformdocs.lattica.ai/architecture-overview/management-client.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.