docs/org settings: Use "full member" terminology.

This commit modifies the help documentation and templates to use a "full
member"/"new member" terminology throughout.

With some tweaks by tabbott.

static/templates/settings/organization-permissions-admin.handlebars

@@ -68,6 +68,7 @@
                 <div class="input-group">
                     <label for="realm_waiting_period_setting" class="dropdown-title">
                         {{t "Waiting period before new members turn into full members" }}
+                        <a href="/help/configure-waiting-period-for-full-members" target="_blank">(?)</a>
                     </label>
                     <select name="realm_waiting_period_setting" id="id_realm_waiting_period_setting" class="prop-element">
                         <option value="none">{{t "None" }}</option>

templates/zerver/help/configure-waiting-period-for-full-members.md

@@ -0,0 +1,35 @@
+# Waiting period for full members
+
+{!admin-only.md!}
+
+Some organization settings allow permissions to be limited to all members or just full members.
+Full members are members whose accounts are older than the configured waiting period which can be
+configured as:
+
+* **No waiting period**
+* **Members with accounts less than 3 days old**
+* **Members with accounts less than N days old**, for some `N`.
+
+This functionality can be useful to limit what "disruptive features" a new user has access to
+until they are familiar with Zulip and the rules of your organization.
+
+For large Zulips where anyone can join, we recommend setting the waiting period
+to at least a few days old (we suggest starting with `N = 3`), to make it easier to cope with
+spammers and confused users.
+
+Currently, the following permissions support limiting access to only full members:
+
+- [**Configure who can create streams**](/help/configure-who-can-create-streams)
+- [**Configure who can invite to streams**](/help/configure-who-can-invite-to-streams)
+
+### Manage the waiting period
+
+{start_tabs}
+
+{settings_tab|organization-permissions}
+
+2. Under **Other permissions**, configure **Waiting period before new members turn into full members**.
+
+{!save-changes.md!}
+
+{end_tabs}

templates/zerver/help/configure-who-can-create-streams.md

@@ -5,18 +5,14 @@
 By default, anyone other than guests can create new streams. However, you can restrict stream
 creation to:
 
-* **Organization administrators and members**
 * **Organization administrators**
-* **Organization administrators, and members with accounts at least `N` days old**, for some `N`.
+* **Organization administrators and all members**
+* **Organization administrators and [full members](/help/configure-waiting-period-for-full-members)**
 
 For corporations and other entities with controlled access, we highly
 recommend keeping stream creation open. A typical Zulip organization with
 heavy use has as many streams as users.
 
-For large Zulips where anyone can join, we recommend restricting stream
-creation to those with accounts at least a few days old (we suggest starting
-with `N = 3`), to make it easier to cope with spammers and confused users.
-
 ### Manage who can create streams
 
 {start_tabs}

templates/zerver/help/configure-who-can-invite-to-streams.md

@@ -5,15 +5,13 @@
 By default, anyone other than guests can invite others to streams. However, you can restrict stream
 invitation to:
 
-* **Organization administrators and members**
 * **Organization administrators**
-* **Organization administrators, and members with accounts at least `N` days old**, for some `N`.
+* **Organization administrators and all members**
+* **Organization administrators and [full members](/help/configure-waiting-period-for-full-members)**
 
 For corporations and other entities with controlled access, we highly
-recommend keeping stream invitation open.
+recommend keeping stream invitation open. For entities with lots of streams with confidential
-
+contents, it may be desirable to limit invitations.
-For entities with lots of streams with confidential contents, it may be desirable
-to limit invitations.
 
 ### Manage who can create streams
 

templates/zerver/help/include/sidebar_index.md

@@ -116,6 +116,7 @@
 * [GDPR Compliance](/help/gdpr-compliance)
 
 ## Organization settings
+* [Waiting period for full members](/help/configure-waiting-period-for-full-members)
 * [Restrict stream creation](/help/configure-who-can-create-streams)
 * [Restrict stream invitation](/help/configure-who-can-invite-to-streams)
 * [Change who can add custom emoji](/help/only-allow-admins-to-add-emoji)

templates/zerver/help/moderating-open-organizations.md

@@ -17,6 +17,9 @@ Moderation is a big part of making an open community work.
 * Create at least one
   [default stream](/help/set-default-streams-for-new-users) where
   [only admins can post](/help/announcement-only-streams).
+* Configure a [waiting period](/help/configure-waiting-period-for-full-members)
+  before new members in the organization can do disruptive actions like creating
+  streams.
 
 ## Response
 

templates/zerver/security.md

@@ -48,13 +48,17 @@ priority.
   projects), to requiring an invitation to join, to having an email from a
   list of domains, to being a member of a specific organization in
   LDAP/Active Directory.
+- Zulip can limit the features that new users have access to until their
+  accounts are older than a [configurable waiting period][waiting_period].
 - Zulip also supports customizing whether non-admins can
   [create streams](/help/configure-who-can-create-streams),
+  [invite to streams](/help/configure-who-can-invite-to-streams),
   [add custom emoji](/help/only-allow-admins-to-add-emoji),
   [add integrations and bots](/help/restrict-bot-creation),
   [edit or delete messages](/help/configure-message-editing-and-deletion),
   and more.
 
+[waiting_period]: /help/configure-waiting-period-for-full-members
 [ldap-name]: https://zulip.readthedocs.io/en/latest/production/authentication-methods.html#ldap-including-active-directory
 
 ## Authentication