From f4290dbb2b05f63bc592b701c264ae3883ebfc84 Mon Sep 17 00:00:00 2001 From: Half-Shot Date: Wed, 4 May 2022 18:34:00 +0000 Subject: deploy: 2d74a8c17876ed235249b1423d63c920c614a530 --- develop/usage/configuration/config_documentation.html | 11 +++++++++++ 1 file changed, 11 insertions(+) (limited to 'develop/usage/configuration/config_documentation.html') diff --git a/develop/usage/configuration/config_documentation.html b/develop/usage/configuration/config_documentation.html index ed8c88e46a..0603e07295 100644 --- a/develop/usage/configuration/config_documentation.html +++ b/develop/usage/configuration/config_documentation.html @@ -660,6 +660,17 @@ session. Defaults to 0.

mau_trial_days: 5
 

+

Config option: mau_appservice_trial_days

+

The option mau_appservice_trial_days is similar to mau_trial_days, but applies a different +trial number if the user was registered by an appservice. A value +of 0 means no trial days are applied. Appservices not listed in this dictionary +use the value of mau_trial_days instead.

+

Example configuration:

+
mau_appservice_trial_days: 
+  my_appservice_id: 3
+  another_appservice_id: 6
+
+

Config option: mau_limit_alerting

The option mau_limit_alerting is a means of limiting client-side alerting should the mau limit be reached. This is useful for small instances -- cgit 1.5.1