> For the complete documentation index, see [llms.txt](https://docs.tuplo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tuplo.com/tuplo-account-management-guide/your-tuplo-dashboard/license.md).

# License

View and Manage acti.

<figure><img src="https://3633098189-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV0nc9z5ERStcxnY8SDZS%2Fuploads%2FqICMzIgLmYi2G9Td1G9U%2Fdashboard-licenses.webp?alt=media&amp;token=c4efcaac-a5bf-4902-be38-5de3417fc1ad" alt=""><figcaption><p>The License section of your Dashboard.</p></figcaption></figure>

This section contains details related to your current license. You can also manage active seats and remove unused seats as needed.

***

## Active Seats

When you or your staff access Tuplo Studio on a computer for the first time, a prompt will request a name for that system. After setting the name, it will count towards your total seat allotments.

To **remove** a seat:

1. **Click** the remove button associated with a seat.
2. **Click** the remove button in the pop-up window to confirm the action.

{% hint style="info" %}
**Quick Tips!**

When all your seats are in use, a prompt will appear when you attempt to log into a new computer. It will state that you either need to remove some seats or add additional ones to your allotment first.
{% endhint %}


---

# 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.tuplo.com/tuplo-account-management-guide/your-tuplo-dashboard/license.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.
