mirror of
https://github.com/zulip/zulip.git
synced 2025-11-10 17:07:07 +00:00
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.
55 lines
2.4 KiB
Markdown
55 lines
2.4 KiB
Markdown
{start_tabs}
|
|
{tab|require-invitations}
|
|
|
|
1. [Configure allowed authentication
|
|
methods](/help/configure-authentication-methods). Zulip offers a variety of
|
|
authentication methods, including email/password, Google, GitHub, GitLab,
|
|
Apple, LDAP and [SAML](/help/saml-authentication). Users can [log
|
|
in][logging-in] with any allowed authentication method, regardless of how
|
|
they signed up.
|
|
|
|
1. Invite users by [sending email invitations][email-invitations] or
|
|
sharing a [reusable invitation link][invitation-links].
|
|
|
|
{tab|allow-anyone-to-join}
|
|
|
|
1. Allow users to [join without an invitation][set-if-invitations-required].
|
|
|
|
1. Configure the appropriate [email domain restrictions][restrict-email-domain]
|
|
for your organization.
|
|
|
|
1. Share a link to your registration page, which is
|
|
https://your-org.zulipchat.com for Zulip Cloud organizations.
|
|
|
|
{tab|imported-organizations}
|
|
|
|
1. [Configure allowed authentication
|
|
methods](/help/configure-authentication-methods). Zulip offers a variety of
|
|
authentication methods, including email/password, Google, GitHub, GitLab,
|
|
Apple, LDAP and [SAML](/help/saml-authentication). Users can immediately [log
|
|
in][logging-in] with any allowed authentication method that does not require
|
|
a password.
|
|
|
|
1. Share a link to your Zulip organization, which is
|
|
https://your-org.zulipchat.com on Zulip Cloud.
|
|
|
|
1. *(optional)* To log in with an email/password, users will need to set their
|
|
initial password. You can:
|
|
|
|
- Automatically send password reset emails to all users in your
|
|
organization. If you imported your organization into Zulip Cloud, simply
|
|
email [support@zulip.com](mailto:support@zulip.com) to request this. Server
|
|
administrators for self-hosted organizations should follow [these
|
|
instructions](/help/import-from-slack#send-password-reset-emails-to-all-users).
|
|
- Let users know that they can [request a password
|
|
reset](/help/change-your-password#if-youve-forgotten-or-never-had-a-password)
|
|
on your organization's login page.
|
|
|
|
{end_tabs}
|
|
|
|
[email-invitations]:/help/invite-new-users#send-email-invitations
|
|
[invitation-links]: /help/invite-new-users#create-a-reusable-invitation-link
|
|
[set-if-invitations-required]: /help/restrict-account-creation#set-whether-invitations-are-required-to-join
|
|
[restrict-email-domain]: /help/restrict-account-creation#configuring-email-domain-restrictions
|
|
[logging-in]: /help/logging-in
|