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/homeserver_sample_config.html | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'develop/usage/configuration/homeserver_sample_config.html') diff --git a/develop/usage/configuration/homeserver_sample_config.html b/develop/usage/configuration/homeserver_sample_config.html index 66fc44a706..ec9c6791ec 100644 --- a/develop/usage/configuration/homeserver_sample_config.html +++ b/develop/usage/configuration/homeserver_sample_config.html @@ -563,6 +563,11 @@ manhole_settings: # sign up in a short space of time never to return after their initial # session. # +# 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. +# # 'mau_limit_alerting' is a means of limiting client side alerting # should the mau limit be reached. This is useful for small instances # where the admin has 5 mau seats (say) for 5 specific people and no @@ -573,6 +578,8 @@ manhole_settings: #max_mau_value: 50 #mau_trial_days: 2 #mau_limit_alerting: false +#mau_appservice_trial_days: +# "appservice-id": 1 # If enabled, the metrics for the number of monthly active users will # be populated, however no one will be limited. If limit_usage_by_mau -- cgit 1.5.1