Skip to content
LibreDrive Docs

Administration guide

This guide covers the tasks an administrator handles from the LibreDrive admin panel, available at /admin once you’re signed in with an administrator account. Every action below is also exposed as a REST endpoint under /api/admin/*, so it can be scripted or wired into your own tooling.

Creating an organization

LibreDrive is multi-tenant: at least one Organization must exist before you can create users. Go to Admin → Organizations, give it a name and a slug, and save. Users, plans, and billing are scoped to the organization they belong to.

Creating storage plans

  1. Go to Admin → Plans.
  2. Give the plan a name (for example Free, Pro, Team), a quota in GB, and optionally a price in cents per billing period — the price only matters once a payment method is enabled, and it’s what LibreDrive uses to generate invoices.
  3. Save. Assign it to a user with PATCH /api/admin/plans/:id/assign/:userId.

Quotas can be changed at any time; existing users on a plan pick up the new limit immediately.

Creating users

  • Admin → Users: enter a name and email and submit. LibreDrive creates the account under your first organization and shows a one-time temporary password — send it to the user yourself, there’s no built-in invite email yet.
  • Open registration: set LIBREDRIVE_ALLOW_SIGNUP=true to let anyone create an account via POST /api/auth/register; new accounts get LIBREDRIVE_DEFAULT_QUOTA unless you assign a plan manually.

Deactivate a user with the Active toggle on their row (PATCH /api/admin/users/:id/active) — this blocks login without deleting their files. Override an individual user’s quota with PATCH /api/admin/users/:id/quota.

Monitoring usage

Admin → Usage shows total storage used across the instance and a per-user breakdown, so you can see who’s consuming the most space before they hit their limit.

Billing and payments

Once a payment method is enabled (see configuration), Admin → Billing lists which providers are active on this instance. From there:

  • Any pending invoice can be marked paid manually, regardless of which providers are enabled — useful for bank transfers or one-off arrangements: POST /api/admin/invoices/:id/mark-paid.
  • An invoice can be voided with POST /api/admin/invoices/:id/void.
  • Per-organization invoice history is available at GET /api/admin/organizations/:id/invoices.

What’s not built yet

A few things mentioned in the product roadmap aren’t in the admin panel yet — see changelog & roadmap for invite-link-based onboarding, per-organization custom subdomains, and two-factor authentication for admin accounts.