> 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-spla-guide/using-your-parallels-spla-subscriptions/managing-your-spla-subscriptions.md).

# Managing your SPLA subscriptions

Parallels My Account allows you to manage your SPLA subscriptions. Using your Parallels account you can perform the following tasks:

* View your Parallels SPLA subscription(s).
* View subscription details, including the license key(s), status, effective dates, next billing date.
* View the list of Parallels RAS farms associated with a subscription with the peak number of concurrent user connections for each farm during the current and previous billing periods.
* View farm details, including daily peak usage numbers for the current or previous billing periods.
* Set a concurrent users limit on a license key that you give to your clients by creating additional license keys.
* View and download your SPLA contract agreement.


---

# 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://docs.parallels.com/landing/ras-spla-guide/using-your-parallels-spla-subscriptions/managing-your-spla-subscriptions.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.