Skip to content

Glossary

A Telegram account listed in admins. Administrators invite people, set quotas, and see the Admin screen. The bot calls them the admin or the server’s owner. A Navidrome administrator is a different role: a Navidrome account that sees every library and can create accounts.

Anyone with an account in the bot: the administrator and everyone they invited. Each participant has a Navidrome account and a personal library.

A participant’s own folder of music, under users in the managed folders. Uploads and imports go here. Only its owner and Navidrome administrators see it.

One library for the whole server, under shared. Participants put tracks here on purpose, and others can take copies into their personal libraries. The bot calls it the Shared Library.

A Navidrome library that holds music outside the bot’s managed folders, usually a collection you had before installing the bot. The bot reads its tracks but never changes the files. Configuration keys call this attaching, as in navidrome.attach_interval.

The folders the bot writes to under library.music_dir: shared, users, and the bot’s working folder .beatstash. They must be on one filesystem.

Where tracks without an artist or title end up. They can be played but not shared.

A limit on the total size of a personal library, or of the shared library. Existing libraries don’t count. See libraries and quotas.

A Navidrome share link. Anyone who has it can play the music without an account until it expires. It needs a public HTTPS address; see HTTPS.

Calling the bot from any Telegram chat by typing @your_music_bot and a query. See sharing.

A private Telegram channel where the bot uploads imported and existing tracks, so it can send them as audio. See storage chat.

A Telegram Bot API server running next to the bot. It lets the bot handle files up to 2000 MiB instead of the cloud API’s 20 MB and 50 MiB limits. See Set up Telegram.

An import downloads a streaming collection into your personal library. Sync runs after the first import and brings in what you saved on the service since. See supported sources.

install.sh from a release. It installs, finishes an interrupted setup, upgrades (bash install.sh upgrade), and uninstalls (bash install.sh uninstall).