Overview
The Session limits page lets you cap how often a lab or track session can be started.
Session limits only apply to sessions that don’t already have a per-participant limit of their own, specifically sessions started from an embed, or from an invite or landing page without its own limit. Sessions started through an invite or landing page that does have a limit aren’t affected, since that limit already caps how many times each participant can start the content.
Default limits
Section titled “Default limits”The Default limits section sets the limits that apply to all content that doesn’t have an override configured.
| Field | Required? | Default | Description |
|---|---|---|---|
| Calendar Month Limit | 0 | Number of times content can be started in the current calendar month | |
| Rolling Month Limit | 0 | Number of times content can be started in a rolling 30-day window | |
| IP Address Per Hour Limit | 0 | Number of times a single IP address can start content within one hour | |
| Concurrent Plays Per IP Address | 0 | Number of simultaneous active sessions a single IP address can have |
A value of 0 means no limit for that field. Values are whole numbers, 0 or greater.
Click Save after changing a value. Save stays disabled until you’ve made a change. This section is read-only unless you have permission to update both track and lab session limits.
Overrides
Section titled “Overrides”The Overrides table lists every lab and track on the team, and lets you set limits for a specific one that take priority over the default limits.
| Column | Description |
|---|---|
| Type | Track or Lab |
| Content | The lab or track name, linking to it. Tracks also show their slug |
| Monthly usage | Number of sessions started for that content in the current calendar month |
| Calendar Month Limit | Override for the calendar month limit |
| Rolling Month Limit | Override for the rolling month limit |
| IP Address Per Hour Limit | Override for the IP address per hour limit |
| Concurrent Plays Per IP Address | Override for the concurrent plays per IP address limit |
Every lab and track appears here whether or not it has an override configured. Its limit columns simply read 0 until you set one.
Leaving an override field at 0 doesn’t turn that limit off. It makes that field fall back to the team’s default limit instead. To have no limit at all for a field on a specific piece of content, the default limit for that same field must also be 0. There’s no separate action to remove an override. Set its fields back to 0 to fall back to the defaults.
Search and filter
Section titled “Search and filter”Use the Search box to filter the table by content name, and the Tracks / Labs checkboxes to filter by content type. Both can be combined, and at least one content type checkbox must stay checked.
Editing an override
Section titled “Editing an override”Editing a row requires permission to update session limits for that row’s content type, tracks and labs are gated separately. If you lack permission for a row, no edit control appears for it.
To set or change an override:
- Find the lab or track in the Overrides table, using search or the type filters if needed.
- Hover the row and click the pencil (edit) icon that appears at its right edge.
- Enter values for the limit fields you want to override. Leave a field at
0to fall back to the team default for that field. - Click Save, or Cancel to discard your changes.
Pagination
Section titled “Pagination”The table paginates at 12 rows by default. Change how many rows are shown per page from the Results per page control in the footer (12, 24, 48, or 96).
Empty state
Section titled “Empty state”If no content matches your search or filters, the table shows No data to display.