diff --git a/java/com.sap.sailing.www/release_notes_admin.html b/java/com.sap.sailing.www/release_notes_admin.html
index de7e8a47c1a..53c68c24f69 100644
--- a/java/com.sap.sailing.www/release_notes_admin.html
+++ b/java/com.sap.sailing.www/release_notes_admin.html
@@ -37,6 +37,34 @@
Administration
+
December 2014
+
+ - We added user management. The /gwt/AdminConsole.html entry point for a fresh server set-up uses
+ admin/admin as username/password. You can change the password in the "Advanced > User Management"
+ tab where also new users can be created. If you assign a use the role "admin" then the user will
+ be able to use the administration console. Stay tuned for a more sophisticated set of roles and
+ permissions to be added in the future.
+
+ - Reverse replication is now possible for selected events. When a replica instance receives a
+ modifying operation, such as a user logging in (creating a user session) or a wind fix being
+ entered through the Race Committee App, this change will be sent from the replica to the master
+ and from there be replicated to all other replicas attached.
+
+ - Starting a server with auto-replication enabled has been changed. The REPLICATE_ON_START environment
+ variable no longer is a Boolean value (True/False) but now has to list the replication services to be
+ replicated from the master. The default environments for replicas at
+ http://releases.sapsailing.com/environments
+ show how this works.
+
+ - The "Connectors" category has a new tab in the administration console, entitled "Regatta Structure Import".
+ If your regatta management system happens to be July 2014
- Replication has become much more robust and efficient. The initial load which used to be sent in a