RegioCloud Admin Β· desktop app
We build it, for our own service, and it is included with every plan. It installs on the administrator's computer and connects directly to your server β the password never passes through us.
Libraries, users and groups in one view, with the three permission levels as columns. One click changes a right. Group rows expand down to the people inside them, marking who also holds a direct share on top β the group-to-person chain that other consoles do not show at all.
The same question, asked backwards: starting from a person, what do they reach? The answer shows each library once, with the strongest right among the paths, but lists every path β ownership, direct share, group membership β and each can be cut separately. It is assembled from five sources, each with its own error channel: a partial answer never appears as a complete one.
The matrix answers for one library. The index answers for one person. The map answers for the entire server at once β every share, wherever it sits, to whom and with which right.
One click writes an Excel file with three sheets: the complete list of shares, the grid, and a coverage sheet stating when the scan ran, what it covered, and β item by item β what failed along the way. That is the difference between a screenshot and a piece of evidence: whoever opens it six months from now knows exactly how far to trust it.
Every share and upload link on the server in one list: who created it, when, how many times it was downloaded, when it expires. Only expired ones carry colour β a future expiry date is neutral information, not an alarm. Revoking happens from the same list.
Version, edition, user and library counts, storage used against storage configured, connected devices. Below them, 7-, 30- or 90-day charts: storage growth, active users, file operations and traffic.
Joiners and leavers
It is what they can still reach: the groups they belonged to, the shares they received directly, the libraries they owned, the links they created. Normally that is four separate places and a list held in someone's head. Here it is a single operation.
Before changing anything, the app gathers all of it: group memberships, direct shares, owned libraries, public links. The plan is drawn on screen, step by step. If a list failed to load, the plan says outright that it may be incomplete β better to say so than to silently revoke less than it promised.
The libraries they owned are not deleted and are not left ownerless: they move to an account you name. The team's work stays exactly where it was, with a new owner.
The revocations run in a single pass, and the account is deactivated at the end. A step that fails does not stop the rest, and you get an itemised tally afterwards: what succeeded and what did not. All of it goes into the log on the Server tab, which cannot be deleted from the app.
Confirming it requires typing the account identifier β an operation this size should not fit inside one mis-click. When someone new joins, the same logic runs backwards: you pick the groups, and you see which libraries come with them before anything is executed.
Every bulk operation draws its full plan first, step by step, and starts only once you approve it. After execution, most changes β a permission level, deactivating an account, revoking an administrator right, removing a group member β can be taken back for a few seconds with an Undo button. Deletions say what they will cost up front, by name.
Until now the badge showed in the list, but granting the right meant a trip to Seafile's web interface. Now the button sits in the account's own row, and a new user can be created as an administrator outright. On the account you are signed in with, the button stays disabled β whichever of your identifiers you used to sign in, because the app asks the server who you are. You cannot lock yourself out.
If you administer more than one Seafile server β your own and a client's, or production and test β connection profiles sit side by side and you switch between them without restarting the app. Each profile keeps its token in the operating system keychain, never in a configuration file.
The app checks for a new version by itself, downloads it in the background and installs it on next launch β an administration operation in progress is never interrupted. Packages are cryptographically signed, and on macOS notarised by Apple as well.