Merge pull request #1320 from zecakeh/master-pushrule

Clarify that `.m.rule.master` has a higher priority than any push rule
This commit is contained in:
Richard van der Hoff 2022-11-08 21:56:39 +00:00 committed by GitHub
commit 498cf6d147
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 10 additions and 6 deletions

View file

@ -0,0 +1 @@
Clarify that `.m.rule.master` has a higher priority than any push rule.

View file

@ -365,18 +365,21 @@ Parameters:
##### Predefined Rules
Homeservers can specify "server-default rules" which operate at a lower
priority than "user-defined rules". The `rule_id` for all server-default
rules MUST start with a dot (".") to identify them as "server-default".
The following server-default rules are specified:
Homeservers can specify "server-default rules". They operate at a lower
priority than "user-defined rules", except for the `.m.rule.master` rule
which has always a higher priority than any other rule. The `rule_id`
for all server-default rules MUST start with a dot (".") to identify
them as "server-default". The following server-default rules are
specified:
###### Default Override Rules
**`.m.rule.master`**
Matches all events. This can be enabled to turn off all push
notifications other than those generated by override rules set by the
user. By default this rule is disabled.
notifications. Unlike other server-default rules, this one has always a
higher priority than other rules, even user defined ones. By default this
rule is disabled.
Definition: