diff --git a/docs/securing-unleash.md b/docs/securing-unleash.md
index 67a4214313..43a1dc3652 100644
--- a/docs/securing-unleash.md
+++ b/docs/securing-unleash.md
@@ -22,6 +22,16 @@ unleash.start({
 });
 ```
 
+Additionally, you can trigger the admin interfact to prompt the user to sign in by configuring your middleware to return a `401` status on
+protected routes. The response body must contain a `message` and a `path` used to redirect the user to the proper login route.
+
+```json
+{
+    "message": "You must be logged in to use Unlseash",
+    "path": "/custom/login"
+}
+```
+
 Examples on custom authentication hooks:
 - [google-auth-hook.js](https://github.com/Unleash/unleash/blob/master/examples/google-auth-hook.js)
 - [basic-auth-hook.js](https://github.com/Unleash/unleash/blob/master/examples/basic-auth-hook.js)
diff --git a/examples/basic-auth-hook.js b/examples/basic-auth-hook.js
index 7d09b27278..ea0c88a765 100644
--- a/examples/basic-auth-hook.js
+++ b/examples/basic-auth-hook.js
@@ -16,7 +16,10 @@ function basicAuthentication(app) {
             return res
                 .status('401')
                 .set({ 'WWW-Authenticate': 'Basic realm="example"' })
-                .end('access denied');
+                .send({
+                    message: 'You must be authenticated to use Unleash',
+                    path: '/custom/login',
+                });
         }
     });