Track limits

Control access to your tracks with 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.

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.

You configure track limits with the web UI.

🌐 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.