diff --git a/docs/manual/src/docbook/session-mgmt.xml b/docs/manual/src/docbook/session-mgmt.xml
index 64a9264127..a00ca41df6 100644
--- a/docs/manual/src/docbook/session-mgmt.xml
+++ b/docs/manual/src/docbook/session-mgmt.xml
@@ -144,5 +144,28 @@
SessionRegistryImpl to be notified when a session ends. Without
it, a user will never be able to log back in again once they have exceeded their session
allowance, even if they log out of another session or it times out.
+
+ Querying the SessionRegistry for currently authenticated
+ users and their sessions
+
+ Setting up concurrency-control, either through the namespace or using plain beans has the
+ useful side effect of providing you with a reference to the SessionRegistry
+ which you can use directly within your application, so even if you don't want to restrict the
+ number of sessions a user may have, it may be worth setting up the infrastructure anyway. You can
+ set the maximumSession property to -1 to allow unlimited sessions. If
+ you're using the namespace, you can set an alias for the internally-created
+ SessionRegistry using the session-registry-alias
+ attribute, providing a reference which you can inject into your own beans.
+
+ The getAllPrincipals()
+ method supplies you with a list of the currently authenticated users. You can list a user's
+ sessions by calling the getAllSessions(Object principal, boolean includeExpiredSessions) method,
+ which returns a list of SessionInformation objects. You can also
+ expire a user's session by calling expireNow() on a
+ SessionInformation instance. When the user returns to the application, they
+ will be prevented from proceeding. You may find these methods useful in an administration
+ application, for example. Have a look at the Javadoc for more information.
+
+