deploy: dcb27783417a1161c484525afb839233299b847f

1 files changed, 2 insertions, 0 deletions

diff --git a/develop/admin_api/user_admin_api.html b/develop/admin_api/user_admin_api.html

index 6ff8503f0e..bdec41080b 100644
--- a/develop/admin_api/user_admin_api.html
+++ b/develop/admin_api/user_admin_api.html
@@ -402,6 +402,7 @@ which guarantees a stable ordering. Valid values are:</p>
 <li><code>displayname</code> - Users are ordered alphabetically by <code>displayname</code>.</li>
 <li><code>avatar_url</code> - Users are ordered alphabetically by avatar URL.</li>
 <li><code>creation_ts</code> - Users are ordered by when the users was created in ms.</li>
+<li><code>last_seen_ts</code> - Users are ordered by when the user was lastly seen in ms.</li>
 </ul>
 </li>
 <li>
@@ -436,6 +437,7 @@ This allows user type specific behaviour. There are also types <code>support</co
 <li><code>displayname</code> - string - The user's display name if they have set one.</li>
 <li><code>avatar_url</code> - string -  The user's avatar URL if they have set one.</li>
 <li><code>creation_ts</code> - integer - The user's creation timestamp in ms.</li>
+<li><code>last_seen_ts</code> - integer - The user's last activity timestamp in ms.</li>
 </ul>
 </li>
 <li>