docs.neptuneplayer.com
Warning: If this is a folder, all contents including subfolders and documents will be deleted.
Define path-based access rules for sections of your wiki, then assign users to groups in the Users tab. Rules are evaluated in order. First match wins.
Create and manage backups of your wiki data. Backups include all documents, images, and configuration files.
Keep your Neptune preferences in sync across every device signed into the same
server account. Settings, layout choices, theme picks, library pins, and your
customized home rows all stay aligned. When one setting genuinely needs to be
different on one device, Device Overrides can
keep that setting local without disabling the rest of sync.
Backup & Restore is currently powered by the Jellyfin-specific Neptune MDM plugin. Without a compatible backend extension, Neptune still works; your settings just stay device-local. Sync support for future backends will be documented as it becomes available.
| Category | Examples |
|---|---|
| Appearance | Theme, theme mode, card styles, layouts, custom theme imports |
| Home & Library layout | Section order and visibility, navigation bar, row limits |
| Playback | Engine choice, autoplay behavior, audio settings, and iOS Picture in Picture and Background Playback toggles |
| Conductor | Languages, track rules, quality preferences |
| Search & AI | Search options and language model configuration |
| Sounds | Theme song volume and behavior |
| Library Pins | Pinned items, browse Pins, timestamp Pins |
| iPhone Compass | Ordered Compass Shortcuts, custom labels and symbols |
| Live Activity | Enabled state and selected activity type |
What stays device-local: diagnostics toggles, the sync switch itself, and
anything tied to the specific hardware. A Device Override is also local, but
it applies to one otherwise synchronized setting. The override list never
travels inside the backup.
Home Screen and Lock Screen widget placement, size, and per-widget
Page/Section/Pin selection are managed by iOS on that device; they are not one
synchronized Neptune preference. The underlying native Pins and the content
Neptune publishes to an existing widget do follow the active profile.
Picture in Picture and Background Playback are synchronized preferences even
though their behavior is iPhone/iPad-only. A changed value is used when the
next playback session starts; it has no effect on Apple TV.
If the plugin is detected on your server, onboarding adds a backup step:
Go to Settings > User Preferences > Backup and Restore:
| Action | Result |
|---|---|
| Sync across devices | The master switch. First save uploads a fresh backup |
| Restore from Backup | Applies the latest synchronized values; active Device Overrides stay local |
| Device Overrides | Keeps selected settings local to this device while everything else syncs |
| Delete Cloud Backup | Removes the backup from the server. Devices keep their local settings and overrides |
With Neptune MDM, rapid local changes are briefly batched and only the settings
that changed are sent to your Jellyfin server. The server merges different
fields into the user's backup, then notifies every other signed-in device.
Those devices apply the accepted changes in place; no restart is needed.
On launch or reconnect, Neptune checks for changes made elsewhere before you
start browsing. Pending local edits are kept until the server accepts them.
If two devices change different settings, both changes can land. If they
change the same setting, the most recently accepted value wins.
An active Device Override removes its setting
from ordinary uploads and downloads on that device. Removing the override
queues this device's current value to sync again.
Deleting the cloud backup clears the server copy but does not erase settings or
Device Overrides from your devices. Neptune will not immediately recreate the
backup just because the app launches or reconnects.
If Settings Sync remains enabled, a later local change can create a new backup
from the current synchronized settings; active overrides remain excluded. Turn
off Sync across devices as well if you want settings to remain local after
deletion.
When an existing installation upgrades to the newer field-level sync system,
Neptune reconciles its earlier local settings with the server backup. If the
app cannot safely tell which copy should win, cloud settings become active and
a one-time Settings Recovery section appears.
Choose Review Which Settings to Keep to keep the cloud version or restore
the retained settings from this device. Restoring the earlier copy makes it
the current synchronized configuration, so those values can update your other
devices. See Device Overrides
for more detail.
The screen shows when the backup was last saved and which device saved it. If sync stops working, a hint explains why (plugin not installed, pending restart, disabled).
| Data | Where It Lives |
|---|---|
| Synchronized settings | On each device, with a backup on your Jellyfin server |
| Device Override list | On that physical device only; never in the cloud backup |
| Authentication | Standard Jellyfin auth tokens |
| Library metadata | Never uploaded as part of sync |
| Watch history | Stays in Jellyfin's own user data, not in the backup |
Sync is scoped per server and per user. A user signed into two different servers maintains two independent backups.