# 6. Plugin Settings
Address: http://localhost:55000/config → Settings tab
Settings let you tune how plugins behave without editing JSON files for every small change.
# How settings work
- Plugins register settings (name, type, default, description).
- Values are stored in a local database.
- Changing a value in the UI saves it and notifies the service.
- Most changes apply immediately.
- Items marked (Requires restart) need a Windows service restart.
Each setting shows:
- Display name and description
- Current control (toggle, number, text)
- Default value
# Common areas you may see
Exact lists depend on which plugins are enabled. Typical examples:
# Folder upload behaviour
- How aggressively missing tracked files are cleaned up
- Retry-related preferences exposed to the UI
- Related operational toggles documented in the description under each control
# Media / Unity monitoring
- Whether to process
mediaitems.json/metricsitems.json - Poll intervals
- Logging detail
# Logging
- Whether file logging is enabled (when exposed as a setting)
Always read the description under a setting — it is written for operators, not just developers.
# Safe workflow for changing settings
- Note the current value (or default).
- Change one setting at a time when diagnosing issues.
- Watch the dashboard logs for a short period.
- If the setting requires restart:
net stop TotumService
net start TotumService(Run from an elevated command prompt.)
# Settings vs Folders vs appsettings
| You want to… | Use |
|---|---|
| Watch a new path / change bucket for a folder | Folders tab |
| Change scan timing, retries, feature toggles | Settings tab |
| Change API keys, base URLs, ports, production secrets | appsettings.Production.json (Advanced) |
# If settings fail to load
- Confirm the service is running
- Check Recent Logs for database errors
- Confirm the
Datafolder next to the executable is writable - See Troubleshooting