> 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

<figure><img src="/files/lu4ZVJDP1SN9f5Oxzw6U" 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 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.tuplo.com/tuplo-account-management-guide/your-tuplo-dashboard/license.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.