> For the complete documentation index, see [llms.txt](https://academy.shade.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.shade.inc/help-center/help-center-es/facturacion/como-funcionan-los-limites-de-asientos.md).

# ¿Cómo funcionan los límites de asientos?

Los puestos (unidades facturables) tienen límites según tu plan de espacio de trabajo.

Por ejemplo, los planes Personal tienen hasta 3 puestos, los planes Starter hasta 5, Growth hasta 15 y Enterprise ilimitado. Ten en cuenta tu número de puestos antes de elegir un plan.

Los puestos se definen como cualquier Propietario del espacio de trabajo, Administrador, Miembro, Colaborador o Contratista; estas son personas que has invitado a nivel de espacio de trabajo (normalmente tu equipo interno o freelancers). Los invitados NO se facturan ni cuentan para tus puestos; sin embargo, cada plan tiene un límite en la cantidad de invitados permitidos en un espacio de trabajo: 5 en Personal, 25 en Starter, 100 en Growth e ilimitado en Enterprise.


---

# 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://academy.shade.inc/help-center/help-center-es/facturacion/como-funcionan-los-limites-de-asientos.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.