# How Streams Manager enforces streaming limits?

Streams Manager provides plan streaming limits enforcement functionality. Each plan can be configured to allow only certain number of simultaneous devices/streams and Streams Manager will then enforce those limits. The process works as follows:

* Every 5 minutes, Streams Manager collects streaming activity on all your media servers
* If server settings have logging of streaming activity enabled, the activity will be logged to the database so it can be reviewed later
* Streaming activity data indicates which user is doing the streaming, from which device, which IP address and from which server
* Streams Manager then checks currently active plan for the user doing the streaming and how many simultaneous devices/streams their plan allows. Streams Manager does not check whether multiple devices are coming from different IP addresses (i.e. it does not enforce IP lock)
* If the user is exceeding their plan limits, all their streams will be stopped and a message will be shown on user's screen indicating that they have too many devices in use
* A notification will be sent to the user also indicating that they have too many devices in use. To modify the content of this notification, see notification templates in settings

On Plex servers, this process requires your Plex account to have a Plex Pass as stopping of the stream feature requires it. If your Plex account does not have it, all the above actions will be performed except of stopping of the stream and showing the message on user's device. Emby and Jellyfin servers are supported as well.

<br>


---

# Agent Instructions: 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:

```
GET https://streamsmanager.gitbook.io/streams-manager/faq/how-streams-manager-enforces-streaming-limits.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.