> For the complete documentation index, see [llms.txt](https://docs.instruqt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.instruqt.com/settings/platform/track-limits.md).

# Track limits

## Overview

Track limits allow you to set a play limit for public track plays. Public plays are all plays through embeds (including LTI-based plays), or through open-ended invites (without restrictions). Plays from team members, and plays from track invites that have limits on the amount of people that can consume the invite do not count towards these limits.

You can configure the following limits:

* Calendar Month Limit\
  Total plays for the current calender month. A calendar month's beginning and finish dates are always fixed (for example, January 1st to January 31st).
* Rolling Month Limit\
  Total plays for the last 30 days.
* IP Address Per Hour Limit\
  The per-IP-per-hour setting limits the total number of plays a single IP address can do per hour for the configured track
* Concurrent Plays Per IP Address\
  Limits the number of plays per track that can be done concurrently from a single IP address.

There is a set of default limits which applies to all tracks, and you can override the configured limits per track.

{% hint style="info" %}
The IP based limits affect the total number of plays a single IP address can do for tracks. When hosting a workshop where the users are on the same network (e.g. during a conference), you can either use an invite with a maximum number of claims (limits do no apply to these type of invites) or temporarily increase the number of plays per IP.
{% endhint %}

You configure track limits with the web UI.

{% tabs %}
{% tab title="🌐 Web UI" %}

1. Click **Settings** → **Track limits**.
2. Set the defaults for the entire team, and click **Save**.
3. Per track, override the team default limits, and click **Save**.
   {% endtab %}
   {% endtabs %}


---

# 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.instruqt.com/settings/platform/track-limits.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.