7ce87c66ac
In our current implementation, loose lists and tight lists look the same visually. Loose lists are lists with blank lines between list items, and the contents of a list item should be enclosed in a paragraph tag in that case. For unordered lists, paragraph tags have a bottom margin in starlight and thus looses lists look much more spaced out than tight lists. That is not the behaviour we had in mind while writing the documentation, the reason we had all these loose lists is to make the documentation easy to write and read. So we attempt to remove all the blank lines and fix the problem at source. Since paragraph tags are used for other purposes in a list in starlight, it won't be a wise decision to let the source be as is and just change things in css, other expected behaviours might break in that case. See this topic for more details: https://chat.zulip.org/#narrow/channel/19-documentation/topic/new.20help.20center.3A.20regressions/near/2226084 All the changes were made by a one-off script which has not been commited to the repo. The script wasn't perfect and could not decide between blank lines that make a list loose vs blank lines necessary for a sub-list or a code block inside a list item. A manual review of all the changes was done before making this commit to ensure that no unintended changes were made to the help center files.
3.3 KiB
Restrict account creation
{!owner-only.md!}
Each Zulip account is associated with an email address. If your organization allows multiple authentication methods, it doesn't matter which one is used to create an account. All authentication methods will work for all users in your organization, provided that they are associated with the account email. To log in with email, users are required to verify their email account by clicking on a validation link.
Zulip provides a number of configuration options to control who can create a new account and how users access their accounts:
- You can require an invitation to sign up (default), or you can allow anyone to join without an invitation.
- You can restrict the ability to invite new users to any combination of roles, groups, and individual users.
Regardless of whether invitations are required, you can:
- Configure allowed authentication methods.
- Restrict sign-ups to a fixed list of allowed domains (including subdomains). For example, you can require users to sign up with the email domain for your business or university.
- Disallow signups with known disposable email address. This is recommended for open organizations to help protect against abuse.
Set whether invitations are required to join
{start_tabs}
{settings_tab|organization-permissions}
- Under Joining the organization, toggle Invitations are required for joining this organization.
{!save-changes.md!}
{end_tabs}
Change who can send invitations
{start_tabs}
{settings_tab|organization-permissions}
- Under Joining the organization, configure Who can send email invitations to new users and Who can create reusable invitation links.
{!save-changes.md!}
{end_tabs}
Configuring email domain restrictions
Email domain restrictions apply to both new user accounts and email changes.
Restrict sign-ups to a list of domains
{start_tabs}
{settings_tab|organization-permissions}
-
Set Restrict email domains of new users to Restrict to a list of domains.
-
Click Configure to add any number of domains. For each domain, you can toggle Allow subdomains.
-
When you are done adding domains, click Close.
{!save-changes.md!}
{end_tabs}
Don't allow disposable domains
{start_tabs}
{settings_tab|organization-permissions}
- Set Restrict email domains of new users to Don't allow disposable emails.
{!save-changes.md!}
{end_tabs}
Allow all email domains
{start_tabs}
{settings_tab|organization-permissions}
- Set Restrict email domains of new users to No restrictions.
{!save-changes.md!}
{end_tabs}