Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-02-25 07:23:42 +01:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Update content/client-server-api/_index.md

Browse source 
Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
This commit is contained in:
Johannes Marbach 2025-08-06 13:18:13 +02:00 committed by GitHub
parent 08ef01beec
commit a644bcd7a1
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 12 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

21
content/client-server-api/_index.md
View file

@ -2506,15 +2506,18 @@ and the client is not permitted to make any changes.
When `enabled` is `true`, clients are permitted to modify profile fields, When `enabled` is `true`, clients are permitted to modify profile fields,
subject to the restrictions implied by the OPTIONAL lists `allowed` and subject to the restrictions implied by the OPTIONAL lists `allowed` and
`disallowed`. If only `allowed` is present, clients can modify all `disallowed`.
contained fields but SHOULD assume all other fields to be managed by
the server. Contrarily, if only `disallowed` is present, clients are If `allowed` is present, clients can modify only the fields
unable to modify any contained fields but SHOULD assume all other fields listed. They SHOULD assume all other fields to be managed by
to be unmanaged. If both `allowed` and `disallowed` are specified, the server. In this case, `disallowed` has no meaning and should be ignored.
`allowed` takes precendece. This means clients can modify all fields
in `allowed` but none of the fields in `disallowed` unless they also If `disallowed` is present (and `allowed` is not), clients should assume
occur in `allowed`. If neither `allowed` nor `disallowed` is present, that the listed fields are managed by the server. Clients may modify any
clients can modify all fields without restrictions. fields that are *not* listed, provided `enabled` is `true`.
If neither `allowed` nor `disallowed` is present, clients can modify all fields
without restrictions, provided `enabled` is `true`.
When not listed, clients SHOULD assume the user is able to change When not listed, clients SHOULD assume the user is able to change
profile fields without any restrictions, provided the homeserver profile fields without any restrictions, provided the homeserver