diff --git a/docs/config-oauth2.md b/docs/config-oauth2.md
index 9bb94c8..ba79aea 100644
--- a/docs/config-oauth2.md
+++ b/docs/config-oauth2.md
@@ -35,6 +35,7 @@ Sometimes, you'll be able to look up the URLs by visiting your provider's
 ```JSON
 {
   "farm": true,
+  "admin": {"oauth2": "ID VALUE FROM OWNER.JSON FILE OF ADMIN"},
   "security_type": "passportjs",
   "oauth2_clientID": "CLIENT ID",
   "oauth2_clientSecret": "CLIENT SECRET",
@@ -48,6 +49,7 @@ Sometimes, you'll be able to look up the URLs by visiting your provider's
 ```JSON
 {
   "farm": true,
+  "admin": {"oauth2": "ID VALUE FROM OWNER.JSON FILE OF ADMIN"},
   "security_type": "passportjs",
   "oauth2_clientID": "CLIENT ID",
   "oauth2_clientSecret": "CLIENT SECRET",
diff --git a/docs/configuration.md b/docs/configuration.md
index 7cf9c09..5c1b41b 100644
--- a/docs/configuration.md
+++ b/docs/configuration.md
@@ -9,7 +9,7 @@ Configuration of Passport security plug-ins is a two stage process:
 
 The legacy Mozilla Persona Passport plug-in does not require any configuration.
 
-This plug-in comes with support for using GitHub, Google, and Twitter. Although the configuration process is broadly the same for each of these, there are some slight differences.
+This plug-in comes with support for using GitHub, Google, Twitter, and generic OAuth. Although the configuration process is broadly the same for each of these, there are some slight differences.
 
 As a wiki server owner you need to pick one, or more, of these that you want to use.