---
{"title": "How church media hosts approve requests from a shared queue", "description": "Steps for church and community media hosts to approve requests from a shared queue, with tool options and common mistakes to avoid.", "url": "https://vlcleanplayer.com/how-to-approve-requests-from-a-shared-queue-for-church-and-community-media-hosts/", "date": "2026-11-01"}
---
Steps for church and community media hosts to approve requests from a shared queue, with tool options and common mistakes to avoid.

To approve requests from a shared queue, name who approves, keep every request in one place, and write short rules for what gets accepted. Askarr is made by the team that publishes this site. Hosted website. [^1][^1]

| Option | Request method | Cost details |
|---|---|---|
| Askarr | Viewers search for a movie or show on Askarr and request it, and your own Radarr and Sonarr add it. [^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] |
| Other tools | not published | not published |

## What you need before you start

Before anyone can approve a request, the host needs a clear list of who may approve, who may send requests, and what kinds of titles the team accepts. Decide these people in advance, so no request sits with no one responsible for it.

Choose the one place where requests will be collected, such as a single shared queue that everyone on the media team can open. Tell the team where that place is, and stop using other channels where requests could pile up unseen.

Agree on the basic approval rules and write them down. Note what a request needs to include, such as the title and its year, and what the approver checks before saying yes. Keep the rules short enough that a volunteer can remember them during a busy week.

Make sure the approvers can see each request and what has already been decided about it, so that no title is approved twice or forgotten. Keep a short note of who handled each decision and when.

## Step by step

1. Name the people who may approve requests, and name a backup approver for weeks when the usual person is away.

2. Set up one shared queue for all requests, and post its location where the team already talks.

3. Write the approval rules in a short note: what a good request looks like, which titles are accepted, and what to do when a title is unclear. Keep the note where approvers can find it.

4. Tell people who send requests what happens after they submit. Say whether they will hear back, and how.

5. Review the queue on the same day each week. For each item, approve it, decline it, or ask for more detail, and record the decision in the queue.

6. Pass approved titles to whoever adds them to the library, and mark each one as handled so no one repeats the work.

7. Once a month, look through the queue for old items and close any that no longer fit the rules.

8. Ask the approvers what slowed them down, then change the rules or the request form to fix it.

## Tools that can do it

Askarr is a hosted website that works with existing Radarr and Sonarr. [^1] There is no app to install; you add Askarr to Radarr and Sonarr as a list they read your requests from. [^1]

You request a movie or show on Askarr, and your own Radarr and Sonarr add it. [^1] A TMDB, IMDb or TVDB link can also be pasted to find a title. [^1] You add Askarr to Radarr and Sonarr one time, and they then read your requests from it. [^1] Askarr never connects to your Radarr or Sonarr and never receives their API keys. [^1]

A bookmark you run on your Radarr or Sonarr page saves the list and webhook there for you. [^1] A webhook, which is an automatic message one program sends another, lets Radarr and Sonarr report back so the site shows when a title was added and downloaded. [^1] Askarr's plans include a request history with live status. [^1] You can try the dashboard with a throwaway demo account and sample data without signing in. [^1]

Other tools are not named here because the source facts do not cover them. Before choosing one, check how it records each decision, who can see the queue, and what it costs. The code behind Askarr is marked as private. [^1]

## Common mistakes to avoid

Avoid letting requests arrive in several places. When people send titles by message, by email, and through a form at the same time, some get lost and others get approved twice. Choose one queue and keep to it.

Avoid approving without agreed rules. If no one wrote down what a good request looks like, each approver will decide differently, and the team will argue about the same title again.

Avoid leaving old requests in the queue. A list that is never cleared becomes hard to read, and new requests can get buried under old ones.

Avoid choosing a tool before checking who can see the queue. Review what each person can see and change before you share the link widely, and make sure the people who approve are the only ones who can record a decision.

## Frequently asked questions

### How can church media hosts approve requests from a shared queue?

Start by naming who approves and writing short rules for what gets accepted. Keep every request in one shared queue so nothing is missed. Review the queue on a set day, record each decision, and pass approved titles to whoever adds them to the library. Tell people who submit requests what happens next, so they are not left waiting for an answer that never comes.

### Does Askarr connect to Radarr and Sonarr?

Askarr never connects to your Radarr or Sonarr and never receives their API keys. [^1] You add Askarr to Radarr and Sonarr once as an import list, and they read your requests from it. [^1] Nothing is installed. [^1] Check this setup with your own Radarr and Sonarr before you rely on it for the whole team.

### Does Askarr have a free plan?

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] Each friend who signs up through your link adds 10 requests a month to your limit. [^1] Match a plan against how many requests your team sends in a month using the plan table.

### Can Askarr be tried before signing up?

You can try the dashboard with a throwaway demo account and sample data without signing in. [^1] Use the demo to look at the request screens and see how a title is found and requested. Then decide whether the set up fits your team before adding Askarr to your own Radarr and Sonarr.

### What should be checked before choosing a request tool for a church media team?

Check how the tool records each decision, who can see the queue, and what it costs each month. Askarr's plans include a request history with live status. [^1] Ask whether the plan you are considering includes request history with live status. [^1] Also check how the tool handles a title that is unclear, since that is where most approval delays start.

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)