diff --git a/config.md b/config.md
index f7759a7..758b8ac 100644
--- a/config.md
+++ b/config.md
@@ -142,4 +142,14 @@ apprise -b "has TagA OR TagB" --tag=TagA --tag=TagB
 # For each item you group with the same --tag value is AND'ed
 apprise -b "has TagA AND TagB" --tag="TagA, TagB"
 apprise -b "has (TagA AND TagB) OR TagC" --tag="TagA, TagB" --tag=TagC
-```
\ No newline at end of file
+```
+
+###  Reserved Tags
+
+The following special tags are reserved for use
+| Tag             | Usage    | Description  |
+| --------------- | -------- |------------- |
+| `always`        | config   | If you store an Apprise entry in a config file and associate the `always` tag with it, it will **ALWAYS** be notified reguardless of any tagging restriction you place on the CLI
+| `all`           | notifications   | When performing a notification, you always have the ability to filter which services are notified based on the tags you've assigned them.  However if you perform a notification and indicate that you want to notify and are filtering on the `all` tag, absolutely everything will be notified (regardless of what other tags have been assigned to it).
+
+It's also worth noting that if you do not assign a tag to an Apprise configuration entry, it can only be actioned/notified if the call to Apprise also does not identify a tag to filter on.  However un-tagged configuration entries will be always included in `all` references.