diff --git a/latest/admin_api/experimental_features.html b/latest/admin_api/experimental_features.html
index 00efb0f9a6..046c6874da 100644
--- a/latest/admin_api/experimental_features.html
+++ b/latest/admin_api/experimental_features.html
@@ -148,11 +148,15 @@
<h1 id="experimental-features-api"><a class="header" href="#experimental-features-api">Experimental Features API</a></h1>
<p>This API allows a server administrator to enable or disable some experimental features on a per-user
-basis. Currently supported features are <a href="https://github.com/matrix-org/matrix-spec-proposals/pull/3026">msc3026</a>: busy
-presence state enabled, <a href="https://github.com/matrix-org/matrix-spec-proposals/pull/2654">msc2654</a>: enable unread counts,
-<a href="https://github.com/matrix-org/matrix-spec-proposals/pull/3881">msc3881</a>: enable remotely toggling push notifications
-for another client, and <a href="https://github.com/matrix-org/matrix-spec-proposals/pull/3967">msc3967</a>: do not require
-UIA when first uploading cross-signing keys. </p>
+basis. The currently supported features are: </p>
+<ul>
+<li><a href="https://github.com/matrix-org/matrix-spec-proposals/pull/3026">MSC3026</a>: busy
+presence state enabled</li>
+<li><a href="https://github.com/matrix-org/matrix-spec-proposals/pull/3881">MSC3881</a>: enable remotely toggling push notifications
+for another client </li>
+<li><a href="https://github.com/matrix-org/matrix-spec-proposals/pull/3967">MSC3967</a>: do not require
+UIA when first uploading cross-signing keys. </li>
+</ul>
<p>To use it, you will need to authenticate by providing an <code>access_token</code>
for a server admin: see <a href="../usage/administration/admin_api/">Admin API</a>.</p>
<h2 id="enablingdisabling-features"><a class="header" href="#enablingdisabling-features">Enabling/Disabling Features</a></h2>
@@ -161,7 +165,7 @@ provide a body containing the user id and listing the features to enable/disable
<pre><code class="language-json">{
"features": {
"msc3026":true,
- "msc2654":true
+ "msc3881":true
}
}
</code></pre>
@@ -178,7 +182,6 @@ user like so:</p>
<pre><code class="language-json">{
"features": {
"msc3026": true,
- "msc2654": true,
"msc3881": false,
"msc3967": false
}
diff --git a/latest/admin_api/statistics.html b/latest/admin_api/statistics.html
index 16f046d5e4..4bf39652a8 100644
--- a/latest/admin_api/statistics.html
+++ b/latest/admin_api/statistics.html
@@ -231,7 +231,7 @@ they are taking.</p>
which means that the returned information can vary widely from reality. However,
it should be enough to get a rough idea of where database disk space is going.</p>
<p>The API is:</p>
-<pre><code>GET /_synapse/admin/v1/statistics/statistics/database/rooms
+<pre><code>GET /_synapse/admin/v1/statistics/database/rooms
</code></pre>
<p>A response body like the following is returned:</p>
<pre><code class="language-json">{
diff --git a/latest/admin_api/user_admin_api.html b/latest/admin_api/user_admin_api.html
index 5501e0dabe..55af2cadb6 100644
--- a/latest/admin_api/user_admin_api.html
+++ b/latest/admin_api/user_admin_api.html
@@ -200,7 +200,7 @@ for a server admin: see <a href="../usage/administration/admin_api/">Admin API</
<ul>
<li><code>user_id</code>: fully-qualified user id: for example, <code>@user:server.com</code>.</li>
</ul>
-<h2 id="create-or-modify-account"><a class="header" href="#create-or-modify-account">Create or modify Account</a></h2>
+<h2 id="create-or-modify-account"><a class="header" href="#create-or-modify-account">Create or modify account</a></h2>
<p>This API allows an administrator to create or modify a user account with a
specific <code>user_id</code>.</p>
<p>This api is:</p>
@@ -209,28 +209,29 @@ specific <code>user_id</code>.</p>
<p>with a body of:</p>
<pre><code class="language-json">{
"password": "user_password",
- "displayname": "User",
+ "logout_devices": false,
+ "displayname": "Alice Marigold",
+ "avatar_url": "mxc://example.com/abcde12345",
"threepids": [
{
"medium": "email",
- "address": "<user_mail_1>"
+ "address": "alice@example.com"
},
{
"medium": "email",
- "address": "<user_mail_2>"
+ "address": "alice@domain.org"
}
],
"external_ids": [
{
- "auth_provider": "<provider1>",
- "external_id": "<user_id_provider_1>"
+ "auth_provider": "example",
+ "external_id": "12345"
},
{
- "auth_provider": "<provider2>",
- "external_id": "<user_id_provider_2>"
+ "auth_provider": "example2",
+ "external_id": "abc54321"
}
],
- "avatar_url": "<avatar_url>",
"admin": false,
"deactivated": false,
"user_type": null
@@ -243,46 +244,74 @@ specific <code>user_id</code>.</p>
</ul>
<p>URL parameters:</p>
<ul>
-<li><code>user_id</code>: fully-qualified user id: for example, <code>@user:server.com</code>.</li>
+<li><code>user_id</code> - A fully-qualified user id. For example, <code>@user:server.com</code>.</li>
</ul>
<p>Body parameters:</p>
<ul>
-<li><code>password</code> - string, optional. If provided, the user's password is updated and all
-devices are logged out, unless <code>logout_devices</code> is set to <code>false</code>.</li>
-<li><code>logout_devices</code> - bool, optional, defaults to <code>true</code>. If set to false, devices aren't
-logged out even when <code>password</code> is provided.</li>
-<li><code>displayname</code> - string, optional, defaults to the value of <code>user_id</code>.</li>
-<li><code>threepids</code> - array, optional, allows setting the third-party IDs (email, msisdn)
+<li>
+<p><code>password</code> - <strong>string</strong>, optional. If provided, the user's password is updated and all
+devices are logged out, unless <code>logout_devices</code> is set to <code>false</code>.</p>
+</li>
+<li>
+<p><code>logout_devices</code> - <strong>bool</strong>, optional, defaults to <code>true</code>. If set to <code>false</code>, devices aren't
+logged out even when <code>password</code> is provided.</p>
+</li>
+<li>
+<p><code>displayname</code> - <strong>string</strong>, optional. If set to an empty string (<code>""</code>), the user's display name
+will be removed.</p>
+</li>
+<li>
+<p><code>avatar_url</code> - <strong>string</strong>, optional. Must be a
+<a href="https://matrix.org/docs/spec/client_server/r0.6.0#matrix-content-mxc-uris">MXC URI</a>.
+If set to an empty string (<code>""</code>), the user's avatar is removed.</p>
+</li>
+<li>
+<p><code>threepids</code> - <strong>array</strong>, optional. If provided, the user's third-party IDs (email, msisdn) are
+entirely replaced with the given list. Each item in the array is an object with the following
+fields:</p>
<ul>
-<li><code>medium</code> - string. Kind of third-party ID, either <code>email</code> or <code>msisdn</code>.</li>
-<li><code>address</code> - string. Value of third-party ID.
-belonging to a user.</li>
+<li><code>medium</code> - <strong>string</strong>, required. The type of third-party ID, either <code>email</code> or <code>msisdn</code> (phone number).</li>
+<li><code>address</code> - <strong>string</strong>, required. The third-party ID itself, e.g. <code>alice@example.com</code> for <code>email</code> or
+<code>447470274584</code> (for a phone number with country code "44") and <code>19254857364</code> (for a phone number
+with country code "1") for <code>msisdn</code>.
+Note: If a threepid is removed from a user via this option, Synapse will also attempt to remove
+that threepid from any identity servers it is aware has a binding for it.</li>
</ul>
</li>
-<li><code>external_ids</code> - array, optional. Allow setting the identifier of the external identity
-provider for SSO (Single sign-on). Details in the configuration manual under the
-sections <a href="../usage/configuration/config_documentation.html#sso">sso</a> and <a href="../usage/configuration/config_documentation.html#oidc_providers">oidc_providers</a>.
+<li>
+<p><code>external_ids</code> - <strong>array</strong>, optional. Allow setting the identifier of the external identity
+provider for SSO (Single sign-on). More details are in the configuration manual under the
+sections <a href="../usage/configuration/config_documentation.html#sso">sso</a> and <a href="../usage/configuration/config_documentation.html#oidc_providers">oidc_providers</a>.</p>
<ul>
-<li><code>auth_provider</code> - string. ID of the external identity provider. Value of <code>idp_id</code>
-in the homeserver configuration. Note that no error is raised if the provided
-value is not in the homeserver configuration.</li>
-<li><code>external_id</code> - string, user ID in the external identity provider.</li>
+<li><code>auth_provider</code> - <strong>string</strong>, required. The unique, internal ID of the external identity provider.
+The same as <code>idp_id</code> from the homeserver configuration. Note that no error is raised if the
+provided value is not in the homeserver configuration.</li>
+<li><code>external_id</code> - <strong>string</strong>, required. An identifier for the user in the external identity provider.
+When the user logs in to the identity provider, this must be the unique ID that they map to.</li>
</ul>
</li>
-<li><code>avatar_url</code> - string, optional, must be a
-<a href="https://matrix.org/docs/spec/client_server/r0.6.0#matrix-content-mxc-uris">MXC URI</a>.</li>
-<li><code>admin</code> - bool, optional, defaults to <code>false</code>.</li>
-<li><code>deactivated</code> - bool, optional. If unspecified, deactivation state will be left
-unchanged on existing accounts and set to <code>false</code> for new accounts.
-A user cannot be erased by deactivating with this API. For details on
-deactivating users see <a href="#deactivate-account">Deactivate Account</a>.</li>
-<li><code>user_type</code> - string or null, optional. If provided, the user type will be
-adjusted. If <code>null</code> given, the user type will be cleared. Other
-allowed options are: <code>bot</code> and <code>support</code>.</li>
+<li>
+<p><code>admin</code> - <strong>bool</strong>, optional, defaults to <code>false</code>. Whether the user is a homeserver administrator,
+granting them access to the Admin API, among other things.</p>
+</li>
+<li>
+<p><code>deactivated</code> - <strong>bool</strong>, optional. If unspecified, deactivation state will be left unchanged.</p>
+<p>Note: the <code>password</code> field must also be set if both of the following are true:</p>
+<ul>
+<li><code>deactivated</code> is set to <code>false</code> and the user was previously deactivated (you are reactivating this user)</li>
+<li>Users are allowed to set their password on this homeserver (both <code>password_config.enabled</code> and
+<code>password_config.localdb_enabled</code> config options are set to <code>true</code>).
+Users' passwords are wiped upon account deactivation, hence the need to set a new one here.</li>
+</ul>
+<p>Note: a user cannot be erased with this API. For more details on
+deactivating and erasing users see <a href="#deactivate-account">Deactivate Account</a>.</p>
+</li>
+<li>
+<p><code>user_type</code> - <strong>string</strong> or null, optional. If not provided, the user type will be
+not be changed. If <code>null</code> is given, the user type will be cleared.
+Other allowed options are: <code>bot</code> and <code>support</code>.</p>
+</li>
</ul>
-<p>If the user already exists then optional parameters default to the current value.</p>
-<p>In order to re-activate an account <code>deactivated</code> must be set to <code>false</code>. If
-users do not login via single-sign-on, a new <code>password</code> must be provided.</p>
<h2 id="list-accounts"><a class="header" href="#list-accounts">List Accounts</a></h2>
<p>This API returns all local user accounts.
By default, the response is ordered by ascending user ID.</p>
|
