diff --git a/changelogs/v0.1.9.md b/changelogs/v0.1.9.md
index 042c1fa..0617a77 100644
--- a/changelogs/v0.1.9.md
+++ b/changelogs/v0.1.9.md
@@ -41,6 +41,7 @@ services:
       - /jellyplist/cookies.txt:/jellyplist/cookies.txt
       - /jellyplist/open.spotify.com_cookies.txt:/jellyplist/spotify-cookie.txt
       - ${MUSIC_STORAGE_BASE_PATH}:${MUSIC_STORAGE_BASE_PATH}
+      - /my/super/cool/storage/jellyplist/settings.yaml:/jellyplist/settings.yaml
     env_file:
       - .env
 
@@ -91,10 +92,41 @@ Set the output folder and file name format for downloaded tracks via spotDL. Not
 This way you will have a bit more controler over how the files are stored. 
 The complete output path is joined from `MUSIC_STORAGE_BASE_PATH` and `SPOTDL_OUTPUT_FORMAT`
 
+_*Example:*_
 
+`MUSIC_STORAGE_BASE_PATH = /storage/media/music`
+
+and 
+
+`SPOTDL_OUTPUT_FORMAT = /{artist}/{album}/{title}`
+
+The Track is _All I Want for Christmas Is You by Mariah Carey_ this will result in the following folder structure:
+
+`/storage/media/music/Mariah Carey/Merry Christmas/All I Want for Christmas Is You.mp3`
+
+### 🆕 Admin Users can now add Playlists to multiple Users
+Sometimes I want to add a playlist to several users at once, because it´s either a _generic_  one or because my wife doesn´t want to bother with the technical stuff 😬
+So now, when logged in as an admin user, when adding a playlist you can select users from your Jellyfin server which will also receive it. 
+Under `Admin` you can also select users which will be preselected by default. These will be stored in the file `settings.yaml`. 
+You can or should map this file to a file outside the container, so it will persist accross image updates (see compose sample above)
+
+### 🆕 New `env` var `QUALITY_SCORE_THRESHOLD`
+Get a better control over the `update_jellyfin_id_for_downloaded_tracks()` behaviour. 
+Until now this tasks performed a __full update__ every 24h: This means, every track from every playlist was searched through the Jellyfin API with the hope of finding the same track but with a better quality. While this is ok and works fine for small libraries, this tasks eats a lot of power on large libraries and also takes time.
+So there is now the new `env` variable  `QUALITY_SCORE_THRESHOLD` (default: `1000.0`). When a track was once found with a quality score above 1000.0, Jellyplist wont try to perform another `quality update` anymore on this track.
+In order to be able to classify it a little better, here are a few common quality scores: 
+- spotDL downloaded track without yt-music premium: `< 300`
+- spotDL downloaded track **with** yt-music premium: `< 450`
+- flac `> 1000`
+
+>[!TIP]
+>Want to know what quality score (and many other details) a track has ? Just double-click the table row in the playlist details view to get all the info´s! 
 
 ### Other changes, improvements and fixes
 - Fix for #38 and #22 , where the manual task starting was missing a return value
 - Fixed an issue where the content-type of a playlist cover image, would cause the Jellyfin API Client to fail. Thanks @artyorsh
 - Fixed missing lock keys to task manager and task status rendering
 - Pinned postgres version to 17.2
+- Enhanced error logging in tasks
+- several fixes and improvements for the Jellyfin API Client
+