diff --git a/USERS.md b/USERS.md
index 614751872e..8cb6553084 100644
--- a/USERS.md
+++ b/USERS.md
@@ -41,6 +41,7 @@ Organizations below are **officially** using Argo Events. Please send a PR with
 1. [ProPoint Solutions](https://supersalon.com)
 1. [PwC Labs](https://www.pwc.com/us/en/careers/why-pwc/what-we-do/what-we-do-pwc-labs.html)
 1. [Rakuten](https://www.rakuten.com)
+1. [Rippling](https://www.rippling.com)
 1. [Rookout](https://www.rookout.com/)
 1. [RTL Nederland](https://www.rtl.nl)
 1. [Salesforce](https://salesforce.com)
diff --git a/docs/eventbus/jetstream.md b/docs/eventbus/jetstream.md
index 2ed190143c..60d7e46a26 100644
--- a/docs/eventbus/jetstream.md
+++ b/docs/eventbus/jetstream.md
@@ -12,6 +12,7 @@ metadata:
 spec:
   jetstream:
     version: latest # Do NOT use "latest" but a specific version in your real deployment
+                    # See: https://argoproj.github.io/argo-events/eventbus/jetstream/#version
 ```
 
 The example above brings up a Jetstream
@@ -26,12 +27,15 @@ for the full spec of `jetstream`.
 
 ### version
 
-The version number specified in the example above is the release number for the NATS server. We will support some subset of these as we've tried them out and only plan to upgrade them as needed. To take a look at what that includes:
+The version number specified in the example above is the release number for the NATS server. We will support some subset of these as we've tried them out and only plan to upgrade them as needed. The list of available versions is managed by the controller manager ConfigMap, which can be updated to support new versions.
 
 ```
 kubectl get configmap argo-events-controller-config -o yaml
 ```
 
+Check [here](https://docs.nats.io/nats-concepts/jetstream/streams#configuration) for a list of configurable features per version.
+
+
 ### A more involved example
 
 Another example with more configuration: