Feature Request: Optional "One In, One Out" Storage Management Policy

[greggathy]

Problem

Many Seerr instances run on servers with finite storage. While requesting media is intentionally simple, there is currently no way to encourage users to free up storage before adding large amounts of new content.

This often results in users requesting multiple long-running TV series or large collections that consume hundreds of gigabytes, while older content they originally requested sits unused. Administrators are then left manually identifying what can be removed or asking users to make those decisions themselves.

It would be useful if Seerr could help users manage their own footprint on the server, while protecting media that has become part of the shared library.

Proposed Solution

Introduce an optional "One In, One Out" request policy.

When a request meets administrator-defined criteria (for example, estimated size, number of seasons, or another configurable threshold), Seerr checks whether the requesting user has previously requested media that is suitable for removal.

If eligible media is found, the user is prompted to choose one or more items to delete before their new request is submitted.

The flow could look like this:

1. User requests new media.
2. Seerr determines whether the request exceeds the configured threshold.
3. If it does, Seerr searches for eligible media previously requested by that user.
4. The user selects one or more items to remove.
5. Seerr sends the deletion request to Radarr/Sonarr.
6. The new request proceeds once the deletion request has been accepted.

If no eligible media is found, the request behaves normally.

Eligibility

By default, eligible media could:

• Have originally been requested by the same user.
• Not have been watched by any other users (using Tautulli data).
• Not currently be downloading or processing.
• Not be protected by administrator rules.

Additional eligibility rules could be configurable.

Why Tautulli?

Tautulli already tracks which users have watched media.

Using this information prevents users from accidentally removing content that has become valuable to others, even if they were the original requester.

For example:

• John requests a 10-season show.
• Only John has watched it.
• Later, John requests another large show.
• Seerr offers the first show as a deletion candidate.

However:

• If Sarah has also watched the show, it would no longer be offered for removal.

This helps preserve the shared nature of the library while still encouraging users to manage their own requests.

Configuration

Everything should be optional and configurable so administrators can tailor the behaviour to their server.

Enablement

• Enable or disable the feature globally.
• Apply to TV only, movies only, or both.

Thresholds

One or more configurable triggers:

• Estimated storage size.
• Number of seasons.
• Number of episodes.
• Estimated runtime.
• Custom "storage cost" score calculated by Seerr.

Candidate Selection

Optional filters:

• Only media requested by the same user.
• Exclude media watched by other users (via Tautulli).
• Ignore media requested within the last X days.
• Ignore media currently being watched.
• Ignore administrator-protected media.
• Minimum age before media becomes eligible.

Matching Rules

Administrators could choose how replacement media is selected:

• Any eligible item.
• Roughly similar estimated storage usage.
• Equal to or greater than the estimated storage cost.
• Multiple smaller items whose combined storage cost satisfies the requirement.

The "similar size" requirement should be optional rather than mandatory, since estimating download sizes is not always reliable.

User Experience

When the policy is triggered, Seerr presents a list of eligible media with useful information, such as:

• Poster and title.
• Request date.
• Last watched date.
• Estimated size (if available).
• Number of users who have watched it.
• Personal watch history.
• Estimated storage that could be reclaimed.

The user selects one or more items, confirms the deletion, and their new request is submitted.

If no eligible media is found, or if the administrator has configured the feature to allow it, the request proceeds as normal.

Benefits

• Reduces manual storage management.
• Gives users ownership over their own library footprint.
• Protects media that other users have watched.
• Helps servers with limited storage remain sustainable.
• Encourages responsible requesting without introducing hard quotas.
• Fits naturally into Seerr's existing request workflow.

Future Enhancements

This feature could also provide a foundation for additional storage management tools, such as:

• Per-user storage budgets.
• Storage usage dashboards.
• Automatic recommendations for unused media.
• Cleanup reminders for inactive requests.
• Optional request quotas or credit-based systems.

I believe this aligns well with Seerr's goal of empowering users while reducing administrative overhead, particularly for self-hosted servers where storage is often the primary limiting resource.

[fallenbagel]

This reads as unreviewed AI output with no AI-assistance disclosure. Per our AI Assistance Notice, that alone is grounds to close it.

Setting that aside, it's out of scope. Seerr is a request management tool, not a storage/library management system. Deletion policies, storage budgets, and watch-tracking-driven cleanup belong in Radarr/Sonarr or other third party applications that support this like Maintainerr, not here. Closing as out of scope.