> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-cpf-integration-guide/custom-provider-framework/functionality-levels.md).

# Functionality Levels

This section outlines the methods required for each supported functionality level of the Custom Provider Framework (CPF). The framework is designed to be implemented incrementally, allowing you to start with a minimal set of capabilities and expand functionality over time as needed.

Not all methods need to be implemented from the outset. At a minimum, only the methods required for the selected functionality level must be supported. Additional methods can be introduced later to enable more advanced features such as template-based deployments, linked clones, or template versioning.

This approach provides flexibility for different use cases:

* **Basic implementations** can focus on simple VM enumeration and control.
* **Intermediate levels** introduce task tracking and template-based provisioning.
* **Advanced implementations** add snapshot management and version control capabilities. 

By following this model, developers can deliver a working integration quickly and progressively enhance it without needing to redesign the provider architecture.

* **Basic**: No templates, only good for creating standalone host pools.
* **Full clones**: Basic support for template host pools by creating copies of the template VM.
* **Link clones**: Can create link clones from a single snapshot of the template VM.
* **Template versions**: Can create full or link clones from different snapshots and can revert the template VM to a specific snapshot (when entering maintenance mode).

<table data-header-hidden="false" data-header-sticky><thead><tr><th>Methods</th><th>Basic</th><th>Full Clones</th><th>Link Clones</th><th>Template Versions</th></tr></thead><tbody><tr><td>Basic</td><td>✅</td><td>✅</td><td>✅</td><td>✅</td></tr><tr><td>Tasks</td><td><strong>❌</strong></td><td>✅</td><td>✅</td><td>✅</td></tr><tr><td>Template</td><td><strong>❌</strong></td><td>✅</td><td>✅</td><td>✅</td></tr><tr><td>Snapshots</td><td><strong>❌</strong></td><td><strong>❌</strong></td><td>✅</td><td>✅</td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.parallels.com/landing/ras-cpf-integration-guide/custom-provider-framework/functionality-levels.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.