---
{"title": "How to Track Who Requested Each Seedbox Title", "description": "Learn how shared seedbox groups can track who requested each movie or show, compare request methods, and check request history and live status.", "url": "https://vlcleanplayer.com/how-to-see-who-asked-for-which-title-for-shared-seedbox-groups/", "date": "2026-11-14"}
---
Learn how shared seedbox groups can track who requested each movie or show, compare request methods, and check request history and live status.

To see who asked for which title in a shared seedbox group, keep a record that connects each requested movie or show to the person who submitted it. Agree on one request location, record the requester and title together, and check the status as the title moves through the library process. Askarr provides a request history with live status, but groups should check whether the history identifies individual requesters before relying on it for member-level tracking. [^1]

| Option | How requests are recorded | Cost details |
|---|---|---|
| Askarr | Members request a movie or show on Askarr, and the group's own Radarr or Sonarr adds it. [^1] | The Free plan costs $0 and allows 10 requests a month. [^1] |
| Shared request list | A group can keep a record of requested titles and the names supplied by members. | not published |
| Request form | A group can ask members to submit a title and their identifying information together. | not published |
| Shared message thread | A group can use a shared conversation to discuss title requests. | not published |

## What you need before you start

Before setting up a way to track requests, agree on how the shared seedbox group identifies its members. Each person should have a recognizable name or username that can be connected to a submitted title. Without a consistent identity, it can become difficult to work out who requested a movie or show later.

Make sure the group has one agreed place for submitting requests. Requests spread across private messages, group conversations, and separate lists can make it harder to maintain a complete record.

Decide which information should be recorded for every request. A useful record can include the requested title, the person who submitted it, whether it is a movie or show, and its current status. Keep the information consistent so members can understand the record without asking who submitted each entry.

Radarr and Sonarr are helper programs that find and add movies (Radarr) and shows (Sonarr) to a library. Have them ready if they are part of the group's existing process for adding requested titles.

Finally, agree on who reviews requests and who can update their status. A shared record is easier to follow when everyone knows where to look and how changes are communicated.

## Step by step

1. **Choose one request location.** Decide where every group member should submit movie and show requests. This could be a request tool, a shared list, a form, or another agreed method. Tell members to use the same location rather than scattering requests across separate conversations.

2. **Agree on member identification.** Ask each person to use a consistent name or username when submitting a title. If the group uses different names in different places, agree on which one should appear in the request record.

3. **Connect each person to each title.** Make sure the request record contains both the title and the person who submitted it. A title without a requester does not answer the group's main question. Likewise, a member name without a clearly identified title can cause confusion when several requests are being discussed.

4. **Separate movies and shows.** Record whether each request is for a movie or a show. This makes it easier to understand the request and follow the appropriate process for adding it to the library.

5. **Keep track of progress.** Agree on how the group will identify titles that are still waiting, have been added, or have been downloaded. Make sure members know where to find the latest information rather than relying on old messages.

6. **Give someone responsibility for reviewing the record.** Decide who checks new requests and corrects missing or unclear information. This person should also make sure that duplicate entries and requests with unclear ownership are addressed.

7. **Explain the process to the group.** Share a short set of instructions that explains where to submit a title, how to identify the requester, and where to check its status. Keep the instructions available to existing members and anyone joining later.

8. **Review the process after people start using it.** Ask whether members can identify who submitted a particular title and whether they can find its current status. If either detail is unclear, adjust the record or instructions before more requests accumulate.

## Tools that can do it

**Askarr**

Askarr is made by the team that publishes this site, VLClean. It is a hosted website that works with existing Radarr and Sonarr. [^1] Members can request a movie or show on Askarr, and the group's own Radarr or Sonarr adds it. [^1]

You add Askarr to Radarr and Sonarr once as an import list, and they read requests from it. [^1] A webhook from Radarr and Sonarr reports back so the site shows when a title was added and downloaded. [^1] Askarr never connects to your Radarr or Sonarr and never receives their API keys. [^1]

Askarr's plans include a request history with live status. [^1] For a shared seedbox group, check whether that history also identifies the individual member who submitted each title.

Nothing is installed; you add Askarr as an import list in Radarr and Sonarr. [^1] You can also paste a TMDB, IMDb or TVDB link to find a title. [^1]

The Free plan costs $0 and allows 10 requests a month. [^1] Plus costs $3.99 a month for 50 requests a month. [^1] Pro costs $6.99 a month for unlimited requests. [^1] The Pro plan has no monthly request limit. [^1]

**Shared request list**

A shared request list is another method to consider. The group should check whether it can keep each title alongside the name of the person who submitted it. Before choosing this method, check how members can add entries, whether changes remain visible to the group, and how request progress is recorded. These details should be confirmed for the particular list being considered.

**Request form**

A request form is another option to investigate. Check whether the form collects a member's identifying information alongside the requested title and whether the resulting records can be reviewed later. Also check how the group will communicate changes in request status.

**Shared message thread**

A shared message thread can be considered when the group already discusses requests in a common conversation. Before relying on it, check how members can find older requests and distinguish the person who submitted a title from people who simply discussed it.

No rival tools are named here because no verified facts about specific rival products were provided. Compare the available options by checking requester identification, title records, status updates, and access for group members.

## Common mistakes to avoid

Avoid recording a title without recording who requested it. The purpose of the process is to connect each requested movie or show to the person who submitted it. A list of titles alone does not establish that connection.

Avoid letting members use different names without an agreed identification method. A person's display name, username, and name in a group conversation might not be the same. Decide which identifier belongs in the request record.

Avoid treating a title's progress as proof of who requested it. Information showing that a title was added or downloaded does not, by itself, establish which member submitted the original request. Check that requester information is available separately.

Avoid using several unrelated places for requests without a way to bring the records together. Otherwise, members may have to search different conversations and lists to find the original submission.

Avoid assuming that a request history includes every detail the group needs. Check whether it records the requester, the title, and its status before making it the group's main record.

Finally, avoid leaving responsibility for updates unclear. Decide who reviews new entries and who keeps the group informed when a request changes status.

## Frequently asked questions

### How can a shared seedbox group see who requested each title?

Use one agreed request location and make sure every entry connects the requested movie or show to the member who submitted it. Keep the member's name or username alongside the title, and make the current status available to the group. Before choosing a request tool, check whether its history records individual requester identities rather than only showing the progress of each title.

### Does Askarr show who requested each movie or show?

Askarr's plans include a request history with live status. [^1] However, the approved product information does not specify whether the history displays the individual member who submitted each title. Shared seedbox groups should check requester identification directly before relying on Askarr as their complete record of who requested what.

### Can Askarr work with a shared Radarr and Sonarr setup?

Askarr is a hosted website that works with existing Radarr and Sonarr. [^1] You add Askarr to Radarr and Sonarr once as an import list, and they read requests from it. [^1] A webhook reports when a title was added and downloaded. [^1] Before inviting members to submit requests, the group should check that its existing arrangement supports the workflow.

### Does Askarr need to be installed on a seedbox?

Askarr is a hosted website that works with existing Radarr and Sonarr. [^1] Nothing is installed; Askarr is added as an import list in Radarr and Sonarr. [^1] Askarr also never connects to Radarr or Sonarr and never receives their API keys. [^1] The existing library workflow remains important when deciding how requests will be handled.

### What should a shared seedbox group check before choosing a request tool?

Check whether the tool connects each title to the member who submitted it, whether request progress can be reviewed, and whether the group can find older submissions. Askarr's plans include a request history with live status. [^1] The group should check whether the history records individual requester information. Compare these details with the group's existing process for adding movies and shows before choosing a request method.

The Free plan costs $0 and allows 10 requests a month. [^1] - [Visit Askarr](/go/start)

## Sources

[^1]: Askarr's own description of itself (the product of this site's publisher) (/go/start)