Skip to content
Storage

Count and storage: both at once

Nexview knows two currencies for quotas, and since 0.19 both always apply.

Jump there →
Screenshot: Count and storage: both at once
Storage

Everything to the house: a button, not a side effect

Sometimes the attribution has grown lopsided: somebody fetched a lot years ago and moved out long since, another sits at 300 GB because they once requested a whole series.

Jump there →
Screenshot: Everything to the house: a button, not a side effect
Storage

Personal account and house inventory

The personal account covers everything this person requested and still claims, movies whole, shows per season, never finer.

Jump there →
Screenshot: Personal account and house inventory
Storage

My storage: seeing what you occupy

The Storage quota tab in the profile shows your own state: occupied space against the limit, and below it every single title, largest first, because whoever is asked to make room must first see where the room went.

Jump there →
Screenshot: My storage: seeing what you occupy
Storage

The watched eyes

The real question behind every clean-up is: „have I even watched this?“ So every title carries an eye: green means watched, red means not yet.

Jump there →
Screenshot: The watched eyes
Storage quotas

Gigabytes instead of counts

“Three movies a week” sounds fair, until one of them is 60 GB. Nexview can therefore measure quotas in the thing that actually matters: occupied storage. This page explains the whole system, the two currencies, the difference between a personal account and the house inventory, handing titles back, the settings, and what happens when an account is deleted.

Still in its test phase. Storage quotas are being tried out in real operation, expect bugs and changes, and if you spot something: report it on GitHub. The app shows the same notice above its settings.

Nobody is limited out of the box, though. The defaults are empty, and empty means unlimited, a freshly updated installation measures without denying anyone anything.

The idea

Storage is not consumed: it is occupied

This is exactly where storage quotas usually fail: space is not used up per person like an allowance, it is occupied jointly. A personal GB account is therefore always a convention, and Nexview makes that convention honest instead of hiding it:

Your account covers what you brought into the house yourself and still claim. The moment the operator takes a title into the house inventory, it belongs to the house, and no longer counts against anyone.

That gives every person a way out that is not deletion: handing back. The operator then decides whether the title stays (and belongs to the house) or really disappears. Psychologically, that is a different product from “delete something or you're stuck”.

Two currencies

Count and storage: both at once

Nexview knows two currencies for quotas, and since 0.19 both always apply. Until then it was one or the other, switchable house-wide; that switch is gone for good. If you only want to limit by count, leave the storage limit empty, and the other way round. Empty means unlimited.

The two behave quite differently, which is exactly why they complement each other: an item quota renews every week or month, against a full week, waiting helps. Storage never renews, because the space is occupied. Against a full account, only tidying up helps.

Because both apply, a request can fail for two reasons, and the message says explicitly which of the two limits was hit. Without that, an administrator would have to guess why somebody can no longer request anything. The item count is checked first: it is the limit you can do nothing about but wait, and learning that first saves a pointless clear-out.

Screenshot: the storage settings with the test-phase notice, the choice between by count and by storage, the default limit, and the queue of pending hand-backs on the right
The control centre. Mode and default limit on the left, hand-backs awaiting a decision on the right, the house's current state below, and the test-phase notice on top.
Switching

Everything to the house: a button, not a side effect

Sometimes the attribution has grown lopsided: somebody fetched a lot years ago and moved out long since, another sits at 300 GB because they once requested a whole series. There is a button for that, every attributed title moves into the house collection, and every account starts at zero.

Until 0.19 this happened as a side effect of switching the accounting mode. The mode is gone; the operation stayed, now as something you do deliberately rather than trigger by accident.

No click goes through quietly: a dialogue states the real numbers beforehand, how many titles with how many GB become house holdings. Numbers instead of a warning, because a general notice gets clicked away and a number gets read. Files are never touched; only who something is charged to changes.

Screenshot: the confirmation dialogue for moving everything to the house — it names the number of titles and the gigabytes before anything happens
Numbers, not warnings. A generic notice gets clicked away, a number gets read. Only the red button executes; cancel leaves everything as it was.
The core

Personal account and house inventory

The personal account covers everything this person requested and still claims, movies whole, shows per season, never finer. Handed-back titles keep counting until the operator has decided; otherwise handing back would be a free pass. 1080p and 4K of the same movie are two files, and therefore two items.

The house inventory belongs to nobody and counts against nobody. Everything already in the library at the first measuring run falls to it, so every account starts at zero. Plus whatever the operator deliberately takes over: “everyone here wants that classic anyway, it should not weigh on your account.”

Whatever an administrator requests belongs to the house from the start, they have no quota, so there is nothing to attribute. And the sizes come from what Radarr, Sonarr and the media server report anyway, no extra queries, no file-system scan.

Screenshot: the administrator's house-inventory view with the total figures and the titles that belong to the house
The operator's view. Their personal account is zero by definition, Nexview shows them what the house holds and how much is occupied overall instead.
For every person

My storage: seeing what you occupy

The Storage quota tab in the profile shows your own state: occupied space against the limit, and below it every single title, largest first, because whoever is asked to make room must first see where the room went. Long lists get search and pages.

If a hand-back is waiting for the operator, that shows in yellow on the row and in the sum: “X GB are awaiting a decision, until then they keep counting.”

The same figure also lives in the account menu at the top right, it is never more than one click away.

Screenshot: the storage quota tab in the profile — occupied space against the limit at the top, below it the own titles sorted by size, each with an eye icon and the button I don't need this
187 of 300 GB. Every row carries its size, its watched eye and the hand-back button. Two titles are already awaiting the operator's decision.
Decision aid

The watched eyes

The real question behind every clean-up is: “have I even watched this?” So every title carries an eye: green means watched, red means not yet. For seasons, green explicitly means every episode watched, half-watched stays red, because for “can this go?” only all-or-nothing counts.

The data comes from the per-person watched sync with Plex. If an account is not linked to the media server, Nexview shows a question-mark eye with the reason, a red eye would claim “never watched” where nobody can actually check.

The Watched only filter above the list shows the hand-back candidates at a glance, it only appears when watched data exists at all.

Screenshot detail: the title list with green and red eyes — watched titles green, unwatched ones red
Green can go. Watched seasons and movies are the natural hand-back candidates, the eye turns the decision into a glance.
When it gets tight

Warn, allow: block only in the red

Nexview blocks a request only when the account is already overdrawn. If there is anything left, the request goes through, even if the title will probably exceed it. Nobody can know in advance how large a file will really be, and blocking on an estimate would be arbitrary.

Whoever is over the limit sees it unmistakably, and cannot request anything new until there is room again. Everything else keeps working: browsing, handing back, the watchlist.

The operator, by the way, sees the requester's state right in the approval list, warned, not blocked: whether to approve despite an overdrawn account remains their call.

Screenshot: an overdrawn account — 71 of 50 GB in red, below it the notice that nothing new can be requested, and titles with question-mark eyes
71 of 50 GB. Over the limit the figure turns red and new requests are blocked until room is made. The question-mark eyes: this account is not linked to Plex.
The flow

Handing back: one click, one wish, one decision

Room is made with I don't need this. For movies, that says it all. For seasons, Nexview asks for the wish: Have it deleted frees the space, Keep, stop downloading leaves the episodes in place and only ends the downloading; the title keeps counting, it just stops growing.

Important: handing back does nothing yet. The title stays on disk and keeps counting until the operator has decided, otherwise you could hand everything back and be instantly free. A slip of the mouse is undone any time with Keep after all.

The operator sees the hand-back in the queue, wish on the row, and has three outcomes: To the house (title stays, account freed, file untouched), Delete (with the actual file list in view, the only step with no way back) or Stop following (episodes stay, downloading ends). The person gets the outcome as a notification.

Screenshot: the wish dialog when handing back a season — the choices are Have it deleted and Keep, stop downloading
The wish travels along. One step, so nobody is asked twice: the person states their wish when handing back, the operator decides exactly once.
Settings in detail

One limit for everyone, refined per account

The default limit in the settings applies to every account that carries nothing of its own, a new account is set up correctly without a single extra step. Empty means: nobody is limited; then Nexview only measures and displays.

In user management, any account can get its own storage limit. The label spells out the semantics: empty = the default limit applies, 0 = this account is unlimited. Administrators are always unlimited, what they fetch belongs to the house anyway.

In count mode the field does not appear at all, a setting without effect would only be a trap.

Screenshot: user management with an account's storage limit field — empty means the default limit, zero means unlimited
Refined per account. The brother-in-law gets 500 GB, the kids 100, and whoever has nothing of their own follows the default.
Honestly

There is one catch

Nexview downloads nothing and deletes nothing itself, everything runs through Radarr and Sonarr. Nexview is meant to complement these apps, not replace them. From that follows the one hard condition: titles must stay in Radarr and Sonarr.

The catch concerns a popular workflow: admins of large libraries like to remove movies from Radarr once the quality profile has hit its maximum, Radarr as a pure download machine, the file stays. With that workflow the storage quota stops working. Such a title remains measurable (the media server still lists it, the account stays honestly charged), but Nexview can no longer delete it, the person can only pass it to the house inventory. That is exactly what the red box in the settings warns about.

And because deleting is the only step with no way back: set up the recycle bin right inside Nexview, the storage settings show for each instance whether one is set, with the field to enter it. The work is then done by Radarr and Sonarr: deleted files move to their recycle bin instead of vanishing immediately, and Nexview says before every deletion which of the two cases applies.

Deleting an account, part 1

The request

Users and approvers do not delete their account themselves, they request it in the profile under Security. The request reaches the operator as an ordinary ticket; a duplicate request is refused while the first one is open.

Until the deletion, nothing changes: requesting, browsing, handing back, everything keeps working. The deletion itself deliberately stays with the operator, because the decision about the estate hangs on it.

Screenshot: the Delete account card in the profile under Account → Security with the Request deletion button
A request, not self-service. The button files the request, the deletion happens later, by the operator, with the estate list in view.
Deleting an account, part 2

What an account leaves behind, a human decides

When the operator deletes the account, they decide about the estate at the same time, list in view, checkbox by checkbox: checked = to the house (file stays), unchecked is deleted through Radarr/Sonarr. “Mark all” handles the most common case in one click.

Running orders are settled too: open ones without a single file are cancelled, started seasons get their own question, keep or delete, and whether to keep downloading. Nothing keeps downloading ownerless after the deletion.

Screenshot: the dialog when deleting an account — a checkbox per title for to the house, below it the summary of how much goes to the house and how much is deleted
Checked = stays. Keeping is the safe default; deleting wants to be chosen deliberately, item by item. Only below that does the account fall, for good.
Tidying up

What nobody has watched for a long time

The statistics have an entry of their own for it: a list of titles nobody has watched in a long while, largest first. Along with how much space each one needs, when it last ran, who watched it, and who it is charged to. Filter by movies or shows, search by title, and set the period from a few months to several years.

Two clocks count, not one. A title appears only if nobody watched it in the chosen period and it has been here at least that long. Without the second clock the list would effectively be sorted by size, and the 60 GB file that arrived yesterday would top it, before anyone had a chance to watch it.

What Nexview does not know, it says: items whose arrival date is missing are counted and named rather than quietly disappearing.

Screenshot: the list of titles nobody has watched in a long time, largest first, with space, last watched and who it is charged to
Largest first. Each row shows the space, when it last ran, who watched it, and who it is charged to. At the top Nexview says plainly whose watch data the list is based on at all.
Deleting

Fourteen days to think, instead of straight away

Marking something does not delete it. It sets a date fourteen days in the future, adjustable up to ninety. Until then the title stays where it is, visibly marked, and one click takes the mark off again.

Anyone who watches it in the meantime cancels the deletion by themselves, without ever learning one was pending. That is the real point of the grace period: it catches exactly the case where a list appears to be right and is wrong anyway.

What is about to disappear is visible to everyone, not just to administrators. The whole purpose of a grace period is that the household notices it; an announcement only its author reads is not one.

Screenshot: the delete dialogue with three ways — cancel, delete now, and a fourteen-day grace period
Three ways, not one. “14 days' grace” is the suggested one; the dialogue adds that the title stays visible to everyone until then, and that deleting goes through Radarr/Sonarr, so it lands in their recycle bin or nowhere at all.
Once a month

A report by mail, if you want it

Nexview can send you a monthly note of what is lying around: at most thirty lines, largest first, with a link straight into the list. Set it up in your profile under notifications.

Off by default. And without a configured mail server and a public address nothing goes out at all, a mail with a button that leads nowhere would be worse than no mail.

Guide

Switching it on in five steps

1. Set up the recycle bin, right inside Nexview. Under Settings → Storage quotas every instance shows whether a recycle bin is set, with the field to enter it; the work is then done by Radarr and Sonarr. Without one, every deletion is final immediately.

2. Pick the mode. Select By storage and save. The dialog states what moves to the house, on first enabling that is simply the whole existing library: every account starts at zero.

3. Set the default limit. Generous at first, or leave it empty and just measure. After a few days the per-account view shows what is realistic; then the limit comes from real numbers instead of guessing.

4. Refine individual accounts. Whoever should get more or less gets their own figure in user management (empty = default, 0 = unlimited).

5. Watch and decide. Hand-backs appear in the queue, grown files announce themselves as notifications, and the overview always shows house, recycle bin and attribution. If it does not work out for you: Reset and turn off, one click, no file touched.

Good to know: shows are counted per season, never per episode, a season is only attributed once it has fully downloaded. If a file later grows noticeably (say, an upgrade to 4K), Nexview tells the person instead of letting the figure climb silently. And 1080p and 4K of the same title keep separate items, they are two files. The one catch is described above: titles must stay in Radarr and Sonarr.