diff --git a/README.rst b/README.rst
index 47f3e6d..4e6800c 100644
--- a/README.rst
+++ b/README.rst
@@ -145,19 +145,36 @@
 
 To enable keystone notification listener, set the `ks_notification_enable`
 to true.
+
 `ks_notifications_allow_requeue` enables requeue feature in case of
 notification processing error. Enable this only when underlying transport
 supports this feature.
 
+`ks_notifications_topic` (defaults to 'notifications') allows to set
+name of the topic to listen for Keystone notifications on. Note that Keystone
+must also be configured to send notifications to this topic.
+If Barbican version and messaging back end support listener pooling,
+it is preferable to leave this value as default and use
+`ks_notifications_pool_name` (see below).
+
+`ks_notifications_pool_name` (Since Queens release) allows to use keystone
+listener together with other applications listening on the same notifications
+topic without interference between services.
+Set it to any distinctive value to enable listener pooling.
+It is enabled by default with pool name 'barbican'.
+Disable it (by setting to empty string) only if underlying messaging transport
+does not support this feature or Barbican is the sole service listening for
+notifications on `ks_notifications_topic` (default is 'notifications') topic.
 
 .. code-block:: yaml
 
     barbican:
       server:
         enabled: true
-        version: ocata
+        version: queens
         ks_notifications_enable: true
         ks_notifications_allow_requeue: true
+        ks_notifications_pool_name: barbican
 
 
 MySQL server has gone away