mirror of
https://github.com/zulip/zulip.git
synced 2025-10-23 04:52:12 +00:00
3a87b467e9
There is no technical reason to block updating the authentication methods for the demo organization when the owner has not yet set an email. If they get locked out of the demo organization when they set an email address for their account, they can just create another demo organization. These organizations are primarily intended to be temporary sandboxes for trying out Zulip. Co-authored-by: Maneesh Shukla <shuklamaneesh24@gmail.com>
21 lines
954 B
Handlebars
21 lines
954 B
Handlebars
<div id="organization-auth-settings" class="settings-section" data-name="auth-methods">
|
|
{{#unless is_owner}}
|
|
<div class='tip'>{{t "Only organization owners can edit these settings."}}</div>
|
|
{{/unless}}
|
|
<form class="admin-realm-form org-authentications-form">
|
|
<div id="org-auth_settings" class="settings-subsection-parent">
|
|
<div class ="subsection-header">
|
|
<h3>{{t "Authentication methods" }}</h3>
|
|
{{> settings_save_discard_widget section_name="auth_settings" }}
|
|
</div>
|
|
|
|
<div>
|
|
<p>{{t "Configure the authentication methods for your organization."}}</p>
|
|
<div id="id_realm_authentication_methods" class="prop-element" data-setting-widget-type="auth-methods">
|
|
{{! Empty div is intentional, it will get populated by a dedicated template }}
|
|
</div>
|
|
</div>
|
|
</div>
|
|
</form>
|
|
</div>
|