Fossil SCM
Clarity fixes to the Email Alerts capability paragraph of forum.wiki
Commit
d6e5754d71b8b8c469189a2eb313de7f4b56ead84cbbf0fb2101428fb2a7f613
Parent
cabc447c689a81c…
1 file changed
+12
-11
+12
-11
| --- www/forum.wiki | ||
| +++ www/forum.wiki | ||
| @@ -173,21 +173,22 @@ | ||
| 173 | 173 | the WriteTrusted capability (4) to users in the <tt>developer</tt> |
| 174 | 174 | category. If you did not give the Read Forum capability (2) to |
| 175 | 175 | <tt>anonymous</tt> above, you should give <tt>developer</tt> that |
| 176 | 176 | capability here if you choose to give it capability 3 or 4. |
| 177 | 177 | |
| 178 | -You must give at least one user or user category the Email Alerts | |
| 179 | -capability (7), else the only people able to sign themselves up for | |
| 180 | -email notifications are those with the Setup or Admin capability. Those | |
| 181 | -users could sign others up via Admin → Notification, but you | |
| 182 | -probably want to give this capability to one of the user categories. | |
| 183 | -Give it to <tt>nobody</tt> if you want anyone to sign up without any | |
| 184 | -restrictions. Give it to <tt>anonymous</tt> if you want the user to | |
| 185 | -solve a simple CAPTCHA before signing up. Give it to <tt>reader</tt> or | |
| 186 | -<tt>developer</tt> if you want only users with Fossil logins to have | |
| 187 | -this ability. (That's assuming you give one or both of these | |
| 188 | -capabilities to every user on your Fossil repository.) | |
| 178 | +If you want to use the email notification feature, by default only those | |
| 179 | +users in the Setup and Admin user categories can make use of it. Grant | |
| 180 | +the Email Alerts capability (7) to give others access to this feature. | |
| 181 | +Alternately, you can handle notification signups outside of Fossil, with | |
| 182 | +a Setup or Admin users manually signing users up via Admin → | |
| 183 | +Notification. You'll want to grant this capability to the | |
| 184 | +<tt>nobody</tt> user category if you want anyone to sign up without any | |
| 185 | +restrictions. Give it to <tt>anonymous</tt> instead if you want the | |
| 186 | +user to solve a simple CAPTCHA before signing up. Or, give it to | |
| 187 | +<tt>reader</tt> or <tt>developer</tt> if you want only users with Fossil | |
| 188 | +logins to have this ability. (That's assuming you give one or both of | |
| 189 | +these capabilities to every user on your Fossil repository.) | |
| 189 | 190 | |
| 190 | 191 | By following this advice, you should not need to tediously add |
| 191 | 192 | capabilities to individual accounts except in atypical cases, such as |
| 192 | 193 | to grant the Moderate Forum capability (5) to an uncommonly |
| 193 | 194 | highly-trusted user. |
| 194 | 195 |
| --- www/forum.wiki | |
| +++ www/forum.wiki | |
| @@ -173,21 +173,22 @@ | |
| 173 | the WriteTrusted capability (4) to users in the <tt>developer</tt> |
| 174 | category. If you did not give the Read Forum capability (2) to |
| 175 | <tt>anonymous</tt> above, you should give <tt>developer</tt> that |
| 176 | capability here if you choose to give it capability 3 or 4. |
| 177 | |
| 178 | You must give at least one user or user category the Email Alerts |
| 179 | capability (7), else the only people able to sign themselves up for |
| 180 | email notifications are those with the Setup or Admin capability. Those |
| 181 | users could sign others up via Admin → Notification, but you |
| 182 | probably want to give this capability to one of the user categories. |
| 183 | Give it to <tt>nobody</tt> if you want anyone to sign up without any |
| 184 | restrictions. Give it to <tt>anonymous</tt> if you want the user to |
| 185 | solve a simple CAPTCHA before signing up. Give it to <tt>reader</tt> or |
| 186 | <tt>developer</tt> if you want only users with Fossil logins to have |
| 187 | this ability. (That's assuming you give one or both of these |
| 188 | capabilities to every user on your Fossil repository.) |
| 189 | |
| 190 | By following this advice, you should not need to tediously add |
| 191 | capabilities to individual accounts except in atypical cases, such as |
| 192 | to grant the Moderate Forum capability (5) to an uncommonly |
| 193 | highly-trusted user. |
| 194 |
| --- www/forum.wiki | |
| +++ www/forum.wiki | |
| @@ -173,21 +173,22 @@ | |
| 173 | the WriteTrusted capability (4) to users in the <tt>developer</tt> |
| 174 | category. If you did not give the Read Forum capability (2) to |
| 175 | <tt>anonymous</tt> above, you should give <tt>developer</tt> that |
| 176 | capability here if you choose to give it capability 3 or 4. |
| 177 | |
| 178 | If you want to use the email notification feature, by default only those |
| 179 | users in the Setup and Admin user categories can make use of it. Grant |
| 180 | the Email Alerts capability (7) to give others access to this feature. |
| 181 | Alternately, you can handle notification signups outside of Fossil, with |
| 182 | a Setup or Admin users manually signing users up via Admin → |
| 183 | Notification. You'll want to grant this capability to the |
| 184 | <tt>nobody</tt> user category if you want anyone to sign up without any |
| 185 | restrictions. Give it to <tt>anonymous</tt> instead if you want the |
| 186 | user to solve a simple CAPTCHA before signing up. Or, give it to |
| 187 | <tt>reader</tt> or <tt>developer</tt> if you want only users with Fossil |
| 188 | logins to have this ability. (That's assuming you give one or both of |
| 189 | these capabilities to every user on your Fossil repository.) |
| 190 | |
| 191 | By following this advice, you should not need to tediously add |
| 192 | capabilities to individual accounts except in atypical cases, such as |
| 193 | to grant the Moderate Forum capability (5) to an uncommonly |
| 194 | highly-trusted user. |
| 195 |