Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/web/templates/settings/organization_permissions_ad...

354 lines
20 KiB
Handlebars
Raw Normal View History

Split out Organization Permissions page.
2017-05-18 14:06:57 +02:00
<div id="organization-permissions" data-name="organization-permissions" class="settings-section">
settings: Remove form-horizontal class from settings template. This commit removes form-horizontal class from form elements in user profile, org profile, org settings and org permission pages. We also add margin-bottom property for select elements in this page. We can safely remove this class since vertical-align property is already present due to other bootstrap CSS. And margin-bottom property for checkbox inputs are added by bootstrap and for text inputs it is handled in app_components.css. The display property for inputs other than checkbox and select elements is set to inline-block by other bootstrap CSS. For checkbox-type inputs browser sets display property to inline-block but it is eventually computed to "block" as the float property is set to left and so it is not required to set display property for checkbox type inputs. We have added CSS for select elements in settings.css which can be removed later once we remove bootstrap for select elements completely.
2023-01-10 11:33:08 +01:00
<form class="admin-realm-form org-permissions-form">
Split out Organization Permissions page.
2017-05-18 14:06:57 +02:00
settings: Use subection-parent div to get subsction. We used id of save-button to get subsection parameter which is passed to get_complete_data_for_subsection. This commit now changes it to instead get subsection from settings-subsection-parent div. We also change the id of settings-subsection-parent div of organization joining settings in this commit to be a more reasonable name as per this change.
2022-12-07 12:16:37 +01:00
<div id="org-join-settings" class="settings-subsection-parent">
org permissions: Restructure org-permissions-admin template. We restructured template to make org-permissions-template have more separated subsections and so that we can easily apply event handlers and selectors to their corresponding subsections (there will be no change in UI). (This is similar to 8b54b08)
2018-03-20 23:18:34 +01:00
<div class="subsection-header">
settings: Fix info icon in header row outside header. This info icon was smaller than similar ones sitting in heading rows, because the icon element was outside the `<h3>` element for the row. Fixes #23801
2023-01-07 00:08:46 +01:00
<h3>
{{t "Joining the organization" }}
settings: Remove unused class. Removed class is not used for any CSS. Also heading is not for the message retention setting.
2023-01-07 00:11:45 +01:00
<i class="fa fa-info-circle settings-info-icon tippy-zulip-tooltip" aria-hidden="true" data-tippy-content="{{t 'Only owners can change these settings.' }}"></i>
settings: Fix info icon in header row outside header. This info icon was smaller than similar ones sitting in heading rows, because the icon element was outside the `<h3>` element for the row. Fixes #23801
2023-01-07 00:08:46 +01:00
</h3>
org-settings: Fix jquery id selector for join organization settings. Fixes the id used to select and disable the properties for org admins on the organization permissions settings tab.
2022-12-08 15:59:19 +01:00
{{> settings_save_discard_widget section_name="join-settings" }}
Split out Organization Permissions page.
2017-05-18 14:06:57 +02:00
</div>
org settings: Change join org permissions to dropdown.
2018-04-05 00:54:31 +02:00
<div class="m-10 inline-block organization-permissions-parent">
<div class="input-group">
org settings: Move invitations required checkbox to the top. This commit moves the "Invitations are required for joining this organization" checkbox in `Organization permissions` settings to the top.
2022-09-13 09:19:08 +02:00
{{> settings_checkbox
setting_name="realm_invite_required"
prefix="id_"
is_checked=realm_invite_required
label=admin_settings_label.realm_invite_required}}
settings: Remove dropdown-title class. We now use "settings-field-label" and "modal-field-label" class on label elements in settings and modals respectively to add the bottom margin which was previously done by "dropdown-title" class as it is better to have more generic names to use on label for all type of inputs.
2024-03-29 07:54:50 +01:00
<label for="realm_invite_to_realm_policy" class="settings-field-label">{{t "Who can send email invitations to new users" }}
setting: Allow only owners to change "Who can invite users" setting.
2021-07-19 11:47:42 +02:00
</label>
settings: Add settings_select class to select elements. This commit adds settings_select class to select elements in user and organization settings, such that we can add CSS using this class and not using "select" as selector so that we can easily add a select element in future with different CSS if needed.
2023-02-16 10:57:08 +01:00
<select name="realm_invite_to_realm_policy" id="id_realm_invite_to_realm_policy" class="prop-element settings_select bootstrap-focus-style" data-setting-widget-type="number">
settings: Add nobody option for invite_to_realm_policy in frontend.
2021-07-18 18:18:28 +02:00
{{> dropdown_options_widget option_values=invite_to_realm_policy_values}}
org settings: Change user joining invitation setting to dropdown.
2018-04-30 18:26:59 +02:00
</select>
</div>
settings: Extract template file for group setting pill UI. This helps in writing same code again and again for different settings. Can also update group settings to use this template in further commits.
2024-10-30 04:16:57 +01:00
{{> group_setting_value_pill_input
setting_name="realm_create_multiuse_invite_group"
label=(t 'Who can create reusable invitation links')}}
invites: Frontend changes for adding the new realm setting. This commit does the changes in frontend required for adding the new setting `Who can create multiuse invite link.` Fixes #15159.
2023-08-03 16:06:40 +02:00
org settings: Change user joining invitation setting to dropdown.
2018-04-30 18:26:59 +02:00
<div class="input-group">
help: Consistently name restrict email setting. Remove question mark. See https://chat.zulip.org/#narrow/channel/101-design/topic/name.20permissions.20settings.20consistently/near/1959774
2024-10-14 14:32:45 +02:00
<label for="realm_org_join_restrictions" class="settings-field-label">{{t "Restrict email domains of new users" }}</label>
settings: Fix updating realm join restrictions setting. This commit fixes the bug when updating "Restrict email domains of new users?" setting by adding data-setting-widget-type attribute to the select element as get_input_element_value now expects every element to have that attribute after 64c8262eafb. Due to this change, we also need to update the code in populate_data_for_request function to not send invalid parameter in the request. This change resulted in some refactoring which now helps in not passing in the "disallow_disposable_email_addresses" and "email_restricted_to_domains" when these fields are not changed.
2024-05-21 17:59:05 +02:00
<select name="realm_org_join_restrictions" id="id_realm_org_join_restrictions" class="prop-element settings_select bootstrap-focus-style" data-setting-widget-type="string">
org settings: Change join org permissions to dropdown.
2018-04-05 00:54:31 +02:00
<option value="no_restriction">{{t "No restrictions" }}</option>
<option value="no_disposable_email">{{t "Don’t allow disposable email addresses" }}</option>
<option value="only_selected_domain">{{t "Restrict to a list of domains" }}</option>
</select>
settings: Rename dependent-block class to dependent-settings-block. This commit renames dependent-block class to dependent-settings-block and also moves the CSS to app_components.css. This class will now only be used for this particular type of custom inputs and thus we do not need ID in the selectors for applying the CSS.
2022-11-21 11:39:51 +01:00
<div class="dependent-settings-block">
settings: Move custom input div inside the main setting div. This commit moves "dependent-block" div inside the main setting "input-group" div as the custom input is part of that setting only. Also this will help in further refactoring of settings code which will be done in next couple of PRs. There are no changes visually, the space between settings and inputs remain same.
2022-08-31 20:16:01 +02:00
<p id="allowed_domains_label" class="inline-block"></p>
settings: Disable "Joining the organization" settings for admins. This commit disables the settings in "Joining the organization" subsection for admins as they can be changed by only owners. We also move the tooltip mentioning "Only owners can change..." to the subsection heading.
2021-07-29 13:53:27 +02:00
{{#if is_owner }}
settings: Move custom input div inside the main setting div. This commit moves "dependent-block" div inside the main setting "input-group" div as the custom input is part of that setting only. Also this will help in further refactoring of settings code which will be done in next couple of PRs. There are no changes visually, the space between settings and inputs remain same.
2022-08-31 20:16:01 +02:00
<a id="show_realm_domains_modal" role="button">{{t "[Configure]" }}</a>
{{/if}}
</div>
org permissions: Restructure org-permissions-admin template. We restructured template to make org-permissions-template have more separated subsections and so that we can easily apply event handlers and selectors to their corresponding subsections (there will be no change in UI). (This is similar to 8b54b08)
2018-03-20 23:18:34 +01:00
</div>
settings: Refactor code for waiting period setting. This commit refactors code for realm waiting period setting to be similar to other time-based inputs. We also add the code to disable the save button when custom inputs have invalid values.
2022-12-12 18:21:08 +01:00
<div class="input-group time-limit-setting">
settings: Remove dropdown-title class. We now use "settings-field-label" and "modal-field-label" class on label elements in settings and modals respectively to add the bottom margin which was previously done by "dropdown-title" class as it is better to have more generic names to use on label for all type of inputs.
2024-03-29 07:54:50 +01:00
<label for="realm_waiting_period_threshold" class="settings-field-label">
settings: Reorganize options/sections in `Organization Permissions`. As a consequence of too many options in the bottom `Other permissions` subsection, the `Save` button could end up too far up from the bottom, such that it might appear offscreen on low-height laptops. We fix this by reorganizing the settings in a way that is both more intuitive and also ensures that none of the subsections are too tall. Fixes: #14274.
2020-03-23 21:51:27 +01:00
{{t "Waiting period before new members turn into full members" }}
templates: Extract help link widget. This block of html is used at many places so it's a good idea to create a template for it.
2020-05-15 20:43:31 +02:00
{{> ../help_link_widget link="/help/restrict-permissions-of-new-members" }}
settings: Reorganize options/sections in `Organization Permissions`. As a consequence of too many options in the bottom `Other permissions` subsection, the `Save` button could end up too far up from the bottom, such that it might appear offscreen on low-height laptops. We fix this by reorganizing the settings in a way that is both more intuitive and also ensures that none of the subsections are too tall. Fixes: #14274.
2020-03-23 21:51:27 +01:00
</label>
settings: Add settings_select class to select elements. This commit adds settings_select class to select elements in user and organization settings, such that we can add CSS using this class and not using "select" as selector so that we can easily add a select element in future with different CSS if needed.
2023-02-16 10:57:08 +01:00
<select name="realm_waiting_period_threshold" id="id_realm_waiting_period_threshold" class="prop-element settings_select bootstrap-focus-style" data-setting-widget-type="time-limit">
settings: Refactor code for waiting period setting. This commit refactors code for realm waiting period setting to be similar to other time-based inputs. We also add the code to disable the save button when custom inputs have invalid values.
2022-12-12 18:21:08 +01:00
{{> dropdown_options_widget option_values=waiting_period_threshold_dropdown_values}}
settings: Reorganize options/sections in `Organization Permissions`. As a consequence of too many options in the bottom `Other permissions` subsection, the `Save` button could end up too far up from the bottom, such that it might appear offscreen on low-height laptops. We fix this by reorganizing the settings in a way that is both more intuitive and also ensures that none of the subsections are too tall. Fixes: #14274.
2020-03-23 21:51:27 +01:00
</select>
settings_org: Rename custom_days option to custom_period. This commit renames custom_days option for realm waiting threshold setting dropdown to custom_period such that we can reuse existing code for similar time-limit settings.
2022-12-09 15:42:11 +01:00
{{!-- This setting is hidden unless `custom_period` --}}
settings: Rename dependent-block class to dependent-settings-block. This commit renames dependent-block class to dependent-settings-block and also moves the CSS to app_components.css. This class will now only be used for this particular type of custom inputs and thus we do not need ID in the selectors for applying the CSS.
2022-11-21 11:39:51 +01:00
<div class="dependent-settings-block">
settings: Rename IDs of waiting-period-threshold setting elements.
2022-12-13 12:32:01 +01:00
<label for="id_realm_waiting_period_threshold_custom_input" class="inline-block">{{t "Waiting period (days)" }}:</label>
<input type="text" id="id_realm_waiting_period_threshold_custom_input"
name="realm_waiting_period_threshold_custom_input"
settings: Rename admin-realm-time-limit-input class. This commit renames admin-realm-time-limit-input class to time-limit-custom-input such that there is no confusion when it is used for stream settings also.
2023-01-16 10:46:45 +01:00
class="time-limit-custom-input"
settings: Move custom input div inside the main setting div. This commit moves "dependent-block" div inside the main setting "input-group" div as the custom input is part of that setting only. Also this will help in further refactoring of settings code which will be done in next couple of PRs. There are no changes visually, the space between settings and inputs remain same.
2022-08-31 20:16:01 +02:00
value="{{ realm_waiting_period_threshold }}"/>
</div>
settings: Reorganize options/sections in `Organization Permissions`. As a consequence of too many options in the bottom `Other permissions` subsection, the `Save` button could end up too far up from the bottom, such that it might appear offscreen on low-height laptops. We fix this by reorganizing the settings in a way that is both more intuitive and also ensures that none of the subsections are too tall. Fixes: #14274.
2020-03-23 21:51:27 +01:00
</div>
Split out Organization Permissions page.
2017-05-18 14:06:57 +02:00
</div>
settings: Reorder options in organization-permissions-admin.handlebars. Also adds <hr>'s to separate the options into sections.
2017-07-12 23:32:14 +02:00
</div>
Split out Organization Permissions page.
2017-05-18 14:06:57 +02:00
settings: Rename "org-subsection-parent" class to "settings-subsection-parent". This commit renames the "org-subsection-parent" class used for organization settings subsections to "settings-subsection-parent" such that we can use same for the stream settings and avoid duplicating code for handling save-discard widget which will be added in future.
2022-11-03 13:18:42 +01:00
<div id="org-stream-permissions" class="settings-subsection-parent">
org permissions: Restructure org-permissions-admin template. We restructured template to make org-permissions-template have more separated subsections and so that we can easily apply event handlers and selectors to their corresponding subsections (there will be no change in UI). (This is similar to 8b54b08)
2018-03-20 23:18:34 +01:00
<div class="subsection-header">
web-i18n: Update frontend translated strings for stream rename channel. Updates translated strings in web/ that do not need updates to any tests. The majority of these strings are also unique to the file/ template that they are in. A few have overlap with one other file. Some changes here update placeholders/variables in these strings to no longer use stream so that all the translation updates for this rename happen at the same time. The exception to this are cases of "<z-stream>" placeholders in these translated strings. Part of the stream to channel rename project.
2024-04-18 15:20:36 +02:00
<h3>{{t "Channel permissions" }}</h3>
settings: Reorganize options/sections in `Organization Permissions`. As a consequence of too many options in the bottom `Other permissions` subsection, the `Save` button could end up too far up from the bottom, such that it might appear offscreen on low-height laptops. We fix this by reorganizing the settings in a way that is both more intuitive and also ensures that none of the subsections are too tall. Fixes: #14274.
2020-03-23 21:51:27 +01:00
{{> settings_save_discard_widget section_name="stream-permissions" }}
Restructure organization settings and permissions. This restructures organization settings and permissions to be more accurately grouped and for the permissions page to not be too long. CHANGES: PROFILE: (this was split out) organization-profile-admin.handlebars: form #1: name description (SUBMIT) avatar: (UPLOAD) (DELETE) SETTINGS: organization-settings-admin.handlebars: language (mostly untouched) message editing: time limit/history/retention message feed: mandatory-topics preview images preview websites PERMISSIONS: organization-permissions-admin.handlebars (mostly stuff was removed) Joining: restrict domains require invite User Identity: name changes email changes Streams/Emoji: creating streams: waiting period (ADDED) adding emojis (SUBMIT) for whole panel The profile group (name, description, avatar) were split into a new page that did not previously exist, and the permissions was stripped of message settings (message editing, message feed), but keeping the "waiting period" input and putting it in the "Streams & custom emoji" section. Fixes: #5844.
2017-08-18 01:23:55 +02:00
</div>
org permissions: Restructure org-permissions-admin template. We restructured template to make org-permissions-template have more separated subsections and so that we can easily apply event handlers and selectors to their corresponding subsections (there will be no change in UI). (This is similar to 8b54b08)
2018-03-20 23:18:34 +01:00
<div class="m-10 inline-block organization-permissions-parent">
settings: Extract template file for group setting pill UI. This helps in writing same code again and again for different settings. Can also update group settings to use this template in further commits.
2024-10-30 04:16:57 +01:00
{{> group_setting_value_pill_input
setting_name="realm_can_create_public_channel_group"
label=(t 'Who can create public channels')}}
settings: Use new group setting to check permission for creating public channels.
2024-05-31 09:49:10 +02:00
settings: Disable spectator access option for limited plans. We also show upgrade banner along with disabling the setting. We also hide the web-public stream creation policy dropdown in such case as we do when enable_spectator_access is False.
2022-05-26 11:43:42 +02:00
{{> upgrade_tip_widget }}
realm: Add option to enable/disable spectator login. We restrict access of messages from web public streams if anonymous login is disabled via `enable_spectator_access`. Display of `Anonymous login` button is now controlled by the value of `enable_spectator_access`. Admins can toggle `enable_spectator_access` via org settings in UI.
2021-10-03 14:16:07 +02:00
{{> settings_checkbox
setting_name="realm_enable_spectator_access"
prefix="id_"
is_checked=realm_enable_spectator_access
settings: Disable spectator access setting when server setting is False. We disable the enable_spectator_access setting when the server level setting, WEB_PUBLIC_STREAMS_ENABLED setting is set to False. This commit adds a new argument is_disabled to settings_checkbox which is used to disable the checkbox and set the color of label accordingly. This commit also adds a help-link besides the label pointing to "/help/web-public-streams" which is shown irrespective of the setting being enabled or disabled. Fixes #20417.
2021-12-02 19:18:32 +01:00
label=admin_settings_label.realm_enable_spectator_access
is_disabled=disable_enable_spectator_access_setting
lint: Ban Help Center relative links without leading /. Such links would likely end up broken if we change our URL scheme to no longer be based around URL fragments.
2022-05-04 20:18:08 +02:00
help_link="/help/public-access-option"}}
settings: Use new group setting to check web-public stream creation. This commit updates code in webapp to use new group-based setting for checking web-public stream creation permission.
2024-07-26 05:42:14 +02:00
{{> ../dropdown_widget_with_label
widget_name="realm_can_create_web_public_channel_group"
label=(t 'Who can create web-public channels')
value_type="number"}}
settings: Use new group setting to private channels creation permission. This commit updates webapp code to use new group based setting to check permission for creating private streams.
2024-06-17 16:06:49 +02:00
settings: Extract template file for group setting pill UI. This helps in writing same code again and again for different settings. Can also update group settings to use this template in further commits.
2024-10-30 04:16:57 +01:00
{{> group_setting_value_pill_input
setting_name="realm_can_create_private_channel_group"
label=(t 'Who can create private channels')}}
settings: Use new group setting to private channels creation permission. This commit updates webapp code to use new group based setting to check permission for creating private streams.
2024-06-17 16:06:49 +02:00
settings: Create an explicit invite_to_stream_policy setting. This commit creates a new organization setting that determines whether a user can invite other users to streams. Previously this was linked to the waiting period threshold, but this was both not documented and overly limiting. With significant tweaks by tabbott to change the database model to not involve two threshhold fields, edit the tests, etc. This requires follow-up work to make the create stream policy setting work how this code implies it should. Fixes #12042.
2019-04-08 19:23:00 +02:00
<div class="input-group">
settings: Remove dropdown-title class. We now use "settings-field-label" and "modal-field-label" class on label elements in settings and modals respectively to add the bottom margin which was previously done by "dropdown-title" class as it is better to have more generic names to use on label for all type of inputs.
2024-03-29 07:54:50 +01:00
<label for="realm_invite_to_stream_policy" class="settings-field-label">{{t "Who can add users to channels" }}</label>
settings: Add settings_select class to select elements. This commit adds settings_select class to select elements in user and organization settings, such that we can add CSS using this class and not using "select" as selector so that we can easily add a select element in future with different CSS if needed.
2023-02-16 10:57:08 +01:00
<select name="realm_invite_to_stream_policy" id="id_realm_invite_to_stream_policy" class="prop-element settings_select bootstrap-focus-style" data-setting-widget-type="number">
settings_config: Use a common object for different policy values. This commit replaces different objects - create_stream_policy_values, invite_to_realm_policy_values and invite_to_stream_policy_values, with a single object common_policy_values. Though invite_to_realm_policy do not use other fields of objects like description, order, etc. but we can keep it as it is for now as we would separate this setting from "Are invitations required...." dropdown and these fields will be used then. This is a prep commit for commits that will add helper functions in settings_data for these policies replacing the usage of page_params object.
2021-04-28 20:39:24 +02:00
{{> dropdown_options_widget option_values=common_policy_values}}
settings: Create an explicit invite_to_stream_policy setting. This commit creates a new organization setting that determines whether a user can invite other users to streams. Previously this was linked to the waiting period threshold, but this was both not documented and overly limiting. With significant tweaks by tabbott to change the database model to not involve two threshhold fields, edit the tests, etc. This requires follow-up work to make the create stream policy setting work how this code implies it should. Fixes #12042.
2019-04-08 19:23:00 +02:00
</select>
</div>
actions: Modify check_message for handling wildcard_mention_policy setting. This commit adds enforcement for sending messages containing wildcard mentions according to wildcard_mention_policy.
2020-09-11 16:11:06 +02:00
<div class="input-group">
settings: Remove dropdown-title class. We now use "settings-field-label" and "modal-field-label" class on label elements in settings and modals respectively to add the bottom margin which was previously done by "dropdown-title" class as it is better to have more generic names to use on label for all type of inputs.
2024-03-29 07:54:50 +01:00
<label for="realm_wildcard_mention_policy" class="settings-field-label">{{t "Who can notify a large number of users with a wildcard mention" }}
settings: Link to help on restrict wildcard mentions. This is necessary to indicate the definition for "large streams" used.
2021-11-12 20:33:35 +01:00
{{> ../help_link_widget link="/help/restrict-wildcard-mentions" }}
</label>
settings: Add settings_select class to select elements. This commit adds settings_select class to select elements in user and organization settings, such that we can add CSS using this class and not using "select" as selector so that we can easily add a select element in future with different CSS if needed.
2023-02-16 10:57:08 +01:00
<select name="realm_wildcard_mention_policy" id="id_realm_wildcard_mention_policy" class="prop-element settings_select bootstrap-focus-style" data-setting-widget-type="number">
actions: Modify check_message for handling wildcard_mention_policy setting. This commit adds enforcement for sending messages containing wildcard mentions according to wildcard_mention_policy.
2020-09-11 16:11:06 +02:00
{{> dropdown_options_widget option_values=wildcard_mention_policy_values}}
</select>
</div>
settings: Reorganize options/sections in `Organization Permissions`. As a consequence of too many options in the bottom `Other permissions` subsection, the `Save` button could end up too far up from the bottom, such that it might appear offscreen on low-height laptops. We fix this by reorganizing the settings in a way that is both more intuitive and also ensures that none of the subsections are too tall. Fixes: #14274.
2020-03-23 21:51:27 +01:00
</div>
</div>
settings: Create an explicit invite_to_stream_policy setting. This commit creates a new organization setting that determines whether a user can invite other users to streams. Previously this was linked to the waiting period threshold, but this was both not documented and overly limiting. With significant tweaks by tabbott to change the database model to not involve two threshhold fields, edit the tests, etc. This requires follow-up work to make the create stream policy setting work how this code implies it should. Fixes #12042.
2019-04-08 19:23:00 +02:00
settings: Make separate section for organization group settings. Fixes #32214.
2024-11-02 04:15:32 +01:00
<div id="org-group-permissions" class="settings-subsection-parent">
<div class="subsection-header">
<h3>{{t "Group permissions" }}
{{> ../help_link_widget link="/help/manage-user-groups" }}
</h3>
{{> settings_save_discard_widget section_name="group-permissions" }}
</div>
<div class="m-10 inline-block organization-permissions-parent">
{{> group_setting_value_pill_input
setting_name="realm_can_manage_all_groups"
label=(t 'Who can administer all user groups')}}
{{> group_setting_value_pill_input
setting_name="realm_can_create_groups"
label=(t 'Who can create user groups')}}
</div>
</div>
settings: Add two realm settings to restrict direct messages. Fixes #24467.
2024-07-08 19:00:08 +02:00
<div id="org-direct-message-permissions" class="settings-subsection-parent">
<div class="subsection-header">
<h3>{{t "Direct message permissions" }}
{{> ../help_link_widget link="/help/restrict-direct-messages" }}
</h3>
{{> settings_save_discard_widget section_name="direct-message-permissions" }}
</div>
settings: Use new pills UI for DM permission settings. We now use pills UI for direct_message_initiator_group and direct_message_permission_group setting.
2024-10-29 14:29:02 +01:00
{{> group_setting_value_pill_input
setting_name="realm_direct_message_permission_group"
label=(t 'Who can authorize a direct message conversation')}}
{{> group_setting_value_pill_input
setting_name="realm_direct_message_initiator_group"
label=(t 'Who can start a direct message conversation')}}
settings: Add two realm settings to restrict direct messages. Fixes #24467.
2024-07-08 19:00:08 +02:00
</div>
settings: Rename "org-subsection-parent" class to "settings-subsection-parent". This commit renames the "org-subsection-parent" class used for organization settings subsections to "settings-subsection-parent" such that we can use same for the stream settings and avoid duplicating code for handling save-discard widget which will be added in future.
2022-11-03 13:18:42 +01:00
<div id="org-msg-editing" class="settings-subsection-parent">
settings: Move message edit settings to "Organization Permissions". The message-editing section of settings is moved from "Organization Settings" to "Organization Permissions", which feels like a more natural place for these settings.
2021-05-25 21:24:12 +02:00
<div class="subsection-header">
settings: Organize message editing and message moving settings. We separate the message editing and message moving settings into different sections. We do not change the help-links for the section headings and keep both of them same linked to "Configure message eiditng and deletion" as we would anyway be changing or spliting this page and can update the links at that time.
2022-10-18 19:32:58 +02:00
<h3>{{t "Message editing" }}
help: Update URLs to match "Restrict message editing and deletion" title. Updates all references to the new URL and adds a URL redirect. Follow up to #24329.
2023-02-09 05:17:34 +01:00
{{> ../help_link_widget link="/help/restrict-message-editing-and-deletion" }}
settings: Move message edit settings to "Organization Permissions". The message-editing section of settings is moved from "Organization Settings" to "Organization Permissions", which feels like a more natural place for these settings.
2021-05-25 21:24:12 +02:00
</h3>
{{> settings_save_discard_widget section_name="msg-editing" }}
</div>
<div class="inline-block organization-settings-parent">
settings: Add checkbox for whether message editing is allowed or not. This commit adds a checkbox for allow_message_editing setting and thus we also remove the "Never" option from the time limit dropdown as unchecking the newly added checkbox will mean the same. We also disable the time limit input if message editing is not allowed. This commit also changes the label for time limit dropdown. Fixes part of #21739.
2022-04-12 09:56:58 +02:00
{{> settings_checkbox
setting_name="realm_allow_message_editing"
prefix="id_"
is_checked=realm_allow_message_editing
label=admin_settings_label.realm_allow_message_editing}}
settings: Organize message editing and message moving settings. We separate the message editing and message moving settings into different sections. We do not change the help-links for the section headings and keep both of them same linked to "Configure message eiditng and deletion" as we would anyway be changing or spliting this page and can update the links at that time.
2022-10-18 19:32:58 +02:00
{{> settings_checkbox
setting_name="realm_allow_edit_history"
prefix="id_"
is_checked=realm_allow_edit_history
label=admin_settings_label.realm_allow_edit_history}}
settings: Modify update_save_button_state to use it for other settings. This commit modifies update_save_button_state such that it can be used for other time-limit settings too.
2022-09-02 18:44:37 +02:00
<div class="input-group time-limit-setting">
settings: Remove dropdown-title class. We now use "settings-field-label" and "modal-field-label" class on label elements in settings and modals respectively to add the bottom margin which was previously done by "dropdown-title" class as it is better to have more generic names to use on label for all type of inputs.
2024-03-29 07:54:50 +01:00
<label for="realm_message_content_edit_limit_seconds" class="settings-field-label">{{t "Time limit for editing messages" }}</label>
settings: Add settings_select class to select elements. This commit adds settings_select class to select elements in user and organization settings, such that we can add CSS using this class and not using "select" as selector so that we can easily add a select element in future with different CSS if needed.
2023-02-16 10:57:08 +01:00
<select name="realm_message_content_edit_limit_seconds" id="id_realm_message_content_edit_limit_seconds" class="prop-element settings_select bootstrap-focus-style" {{#unless realm_allow_message_editing}}disabled{{/unless}} data-setting-widget-type="time-limit">
settings: Move message edit settings to "Organization Permissions". The message-editing section of settings is moved from "Organization Settings" to "Organization Permissions", which feels like a more natural place for these settings.
2021-05-25 21:24:12 +02:00
{{#each msg_edit_limit_dropdown_values}}
settings_config: Change time_limit_dropdown_values to a list. This commit changes time_limit_dropdown_values from map to list like we have email_notifications_batching_period_values. This change will help us in further commits for refactoring the message edit and delete settings related code.
2022-09-01 14:19:14 +02:00
<option value="{{value}}">{{text}}</option>
settings: Move message edit settings to "Organization Permissions". The message-editing section of settings is moved from "Organization Settings" to "Organization Permissions", which feels like a more natural place for these settings.
2021-05-25 21:24:12 +02:00
{{/each}}
</select>
settings: Rename dependent-block class to dependent-settings-block. This commit renames dependent-block class to dependent-settings-block and also moves the CSS to app_components.css. This class will now only be used for this particular type of custom inputs and thus we do not need ID in the selectors for applying the CSS.
2022-11-21 11:39:51 +01:00
<div class="dependent-settings-block">
settings: Move custom input div inside the main setting div. This commit moves "dependent-block" div inside the main setting "input-group" div as the custom input is part of that setting only. Also this will help in further refactoring of settings code which will be done in next couple of PRs. There are no changes visually, the space between settings and inputs remain same.
2022-08-31 20:16:01 +02:00
<label for="id_realm_message_content_edit_limit_minutes" class="inline-block realm-time-limit-label">
{{t 'Duration editing is allowed after posting (minutes)'}}:&nbsp;
</label>
<input type="text" id="id_realm_message_content_edit_limit_minutes"
name="realm_message_content_edit_limit_minutes"
settings: Rename admin-realm-time-limit-input class. This commit renames admin-realm-time-limit-input class to time-limit-custom-input such that there is no confusion when it is used for stream settings also.
2023-01-16 10:46:45 +01:00
class="time-limit-custom-input"
settings: Move custom input div inside the main setting div. This commit moves "dependent-block" div inside the main setting "input-group" div as the custom input is part of that setting only. Also this will help in further refactoring of settings code which will be done in next couple of PRs. There are no changes visually, the space between settings and inputs remain same.
2022-08-31 20:16:01 +02:00
autocomplete="off"
value="{{ realm_message_content_edit_limit_minutes }}"
{{#unless realm_allow_message_editing}}disabled{{/unless}}/>
</div>
settings: Move message edit settings to "Organization Permissions". The message-editing section of settings is moved from "Organization Settings" to "Organization Permissions", which feels like a more natural place for these settings.
2021-05-25 21:24:12 +02:00
</div>
settings: Organize message editing and message moving settings. We separate the message editing and message moving settings into different sections. We do not change the help-links for the section headings and keep both of them same linked to "Configure message eiditng and deletion" as we would anyway be changing or spliting this page and can update the links at that time.
2022-10-18 19:32:58 +02:00
</div>
</div>
settings: Move message edit settings to "Organization Permissions". The message-editing section of settings is moved from "Organization Settings" to "Organization Permissions", which feels like a more natural place for these settings.
2021-05-25 21:24:12 +02:00
settings: Organize message editing and message moving settings. We separate the message editing and message moving settings into different sections. We do not change the help-links for the section headings and keep both of them same linked to "Configure message eiditng and deletion" as we would anyway be changing or spliting this page and can update the links at that time.
2022-10-18 19:32:58 +02:00
<div id="org-moving-msgs" class="settings-subsection-parent">
<div class="subsection-header">
<h3>{{t "Moving messages" }}
settings: Point the "moving messages" help link to the right place.
2023-03-31 23:17:57 +02:00
{{> ../help_link_widget link="/help/restrict-moving-messages" }}
settings: Organize message editing and message moving settings. We separate the message editing and message moving settings into different sections. We do not change the help-links for the section headings and keep both of them same linked to "Configure message eiditng and deletion" as we would anyway be changing or spliting this page and can update the links at that time.
2022-10-18 19:32:58 +02:00
</h3>
{{> settings_save_discard_widget section_name="moving-msgs" }}
</div>
settings: Add `can_move_messages_between_topics_group` realm setting. Added `can_move_messages_between_topics_group` realm setting to replace `edit_topic_policy`.
2024-10-27 17:01:01 +01:00
settings: Use new pills UI for move message permission settings.
2024-10-30 07:50:59 +01:00
{{> group_setting_value_pill_input
setting_name="realm_can_move_messages_between_topics_group"
label=(t 'Who can move messages to another topic')}}
settings: Move message edit settings to "Organization Permissions". The message-editing section of settings is moved from "Organization Settings" to "Organization Permissions", which feels like a more natural place for these settings.
2021-05-25 21:24:12 +02:00
settings: Add move_messages_within_stream_limit_seconds element in UI. This commit adds dropdown for move_messages_within_stream_limit_seconds setting which is used to control for how long the user is allowed to edit topic.
2022-12-22 19:14:23 +01:00
<div class="input-group time-limit-setting">
settings: Remove dropdown-title class. We now use "settings-field-label" and "modal-field-label" class on label elements in settings and modals respectively to add the bottom margin which was previously done by "dropdown-title" class as it is better to have more generic names to use on label for all type of inputs.
2024-03-29 07:54:50 +01:00
<label for="realm_move_messages_within_stream_limit_seconds" class="settings-field-label">{{t "Time limit for editing topics" }} <i>({{t "does not apply to moderators and administrators" }})</i></label>
settings: Add settings_select class to select elements. This commit adds settings_select class to select elements in user and organization settings, such that we can add CSS using this class and not using "select" as selector so that we can easily add a select element in future with different CSS if needed.
2023-02-16 10:57:08 +01:00
<select name="realm_move_messages_within_stream_limit_seconds" id="id_realm_move_messages_within_stream_limit_seconds" class="prop-element settings_select" data-setting-widget-type="time-limit">
settings: Add move_messages_within_stream_limit_seconds element in UI. This commit adds dropdown for move_messages_within_stream_limit_seconds setting which is used to control for how long the user is allowed to edit topic.
2022-12-22 19:14:23 +01:00
{{#each msg_move_limit_dropdown_values}}
<option value="{{value}}">{{text}}</option>
{{/each}}
</select>
<div class="dependent-settings-block">
<label for="id_realm_move_messages_within_stream_limit_minutes" class="inline-block realm-time-limit-label">
{{t 'Duration editing is allowed after posting (minutes)'}}:&nbsp;
</label>
<input type="text" id="id_realm_move_messages_within_stream_limit_minutes"
name="realm_move_messages_within_stream_limit_minutes"
class="time-limit-custom-input"
autocomplete="off"/>
</div>
</div>
settings: Use new pills UI for move message permission settings.
2024-10-30 07:50:59 +01:00
{{> group_setting_value_pill_input
setting_name="realm_can_move_messages_between_channels_group"
label=(t 'Who can move messages to another channel')}}
settings: Add move_messages_between_streams_limit_seconds element in UI. This commit adds dropdown for move_messages_between_streams_limit_seconds setting which is used to control for how long the user is allowed to edit stream.
2023-01-30 12:15:36 +01:00
<div class="input-group time-limit-setting">
settings: Remove dropdown-title class. We now use "settings-field-label" and "modal-field-label" class on label elements in settings and modals respectively to add the bottom margin which was previously done by "dropdown-title" class as it is better to have more generic names to use on label for all type of inputs.
2024-03-29 07:54:50 +01:00
<label for="realm_move_messages_between_streams_limit_seconds" class="settings-field-label">{{t "Time limit for moving messages between channels" }} <i>({{t "does not apply to moderators and administrators" }})</i></label>
settings: Add settings_select class to select elements. This commit adds settings_select class to select elements in user and organization settings, such that we can add CSS using this class and not using "select" as selector so that we can easily add a select element in future with different CSS if needed.
2023-02-16 10:57:08 +01:00
<select name="realm_move_messages_between_streams_limit_seconds" id="id_realm_move_messages_between_streams_limit_seconds" class="prop-element bootstrap-focus-style settings_select" data-setting-widget-type="time-limit">
settings: Add move_messages_between_streams_limit_seconds element in UI. This commit adds dropdown for move_messages_between_streams_limit_seconds setting which is used to control for how long the user is allowed to edit stream.
2023-01-30 12:15:36 +01:00
{{#each msg_move_limit_dropdown_values}}
<option value="{{value}}">{{text}}</option>
{{/each}}
</select>
<div class="dependent-settings-block">
<label for="id_realm_move_messages_between_streams_limit_minutes" class="inline-block realm-time-limit-label">
{{t 'Duration editing is allowed after posting (minutes)'}}:&nbsp;
</label>
<input type="text" id="id_realm_move_messages_between_streams_limit_minutes"
name="realm_move_messages_between_streams_limit_minutes"
class="time-limit-custom-input"
autocomplete="off"/>
</div>
</div>
settings: Create a new "Message deletion" section. Create a new section under "Message editing" and move "Who can delete their own messages" and "Time limit for deleting messages" to the new section. Remove "i" tooltips next to them. Add a label to the new section "Administrators can delete any message." Fixes part of #22892. settings: Add widgets to the new section "Message deletion". Forgot to add settings_save_discard_widget to last commit. This commit add two buttons when a change is made to the subsections. Fixes part of #22892.
2022-10-06 16:28:41 +02:00
</div>
settings: Rename "org-subsection-parent" class to "settings-subsection-parent". This commit renames the "org-subsection-parent" class used for organization settings subsections to "settings-subsection-parent" such that we can use same for the stream settings and avoid duplicating code for handling save-discard widget which will be added in future.
2022-11-03 13:18:42 +01:00
<div id="org-msg-deletion" class="settings-subsection-parent">
settings: Create a new "Message deletion" section. Create a new section under "Message editing" and move "Who can delete their own messages" and "Time limit for deleting messages" to the new section. Remove "i" tooltips next to them. Add a label to the new section "Administrators can delete any message." Fixes part of #22892. settings: Add widgets to the new section "Message deletion". Forgot to add settings_save_discard_widget to last commit. This commit add two buttons when a change is made to the subsections. Fixes part of #22892.
2022-10-06 16:28:41 +02:00
<div class="subsection-header">
<h3>{{t "Message deletion" }}
help: Update links to "Edit a message" and "Delete a message". The series including 0349152f0f490936b250f5b831f0c6cf55aa8b01 split this page into two smaller pages.
2023-08-29 03:09:41 +02:00
{{> ../help_link_widget link="/help/delete-a-message" }}
settings: Create a new "Message deletion" section. Create a new section under "Message editing" and move "Who can delete their own messages" and "Time limit for deleting messages" to the new section. Remove "i" tooltips next to them. Add a label to the new section "Administrators can delete any message." Fixes part of #22892. settings: Add widgets to the new section "Message deletion". Forgot to add settings_save_discard_widget to last commit. This commit add two buttons when a change is made to the subsections. Fixes part of #22892.
2022-10-06 16:28:41 +02:00
</h3>
{{> settings_save_discard_widget section_name="msg-deletion" }}
</div>
<div class="inline-block organization-settings-parent">
settings: Use new pills UI for message delete permissions.
2024-10-30 08:15:27 +01:00
{{> group_setting_value_pill_input
setting_name="realm_can_delete_any_message_group"
label=(t 'Who can delete any message')}}
settings: Add `can_delete_any_message_group` setting. Fixes #30717.
2024-08-15 07:29:15 +02:00
settings: Use new pills UI for message delete permissions.
2024-10-30 08:15:27 +01:00
{{> group_setting_value_pill_input
setting_name="realm_can_delete_own_message_group"
label=(t 'Who can delete their own messages')}}
realm: Replace allow_message_deleting with delete_own_message_policy. This commit replaces 'allow_message_deleting' boolean setting with an integer setting 'delete_own_message_policy'. We have a separate dropdown now for deciding which user-roles can delete messages sent by themselves and the time-limit setting droddown is different. This new setting has two options - everyone and admins only. Other options including moderators will be added further. We also remove the "Never" option from the original time-limit dropdown, as admins are always allowed to delete message. This never option resembled the case of only admins being allowed to delete but this state is now resembled by setting the dropdown to "admins only" and we also disable the time-limit dropdown in this case as admins are allowed to delete irrespective of limit. Note, this setting is only for deleting messages sent by the deleting user themselves, and only admins are allowed to delete messages sent by others as before.
2021-06-08 13:45:14 +02:00
settings: Modify update_save_button_state to use it for other settings. This commit modifies update_save_button_state such that it can be used for other time-limit settings too.
2022-09-02 18:44:37 +02:00
<div class="input-group time-limit-setting">
settings: Remove dropdown-title class. We now use "settings-field-label" and "modal-field-label" class on label elements in settings and modals respectively to add the bottom margin which was previously done by "dropdown-title" class as it is better to have more generic names to use on label for all type of inputs.
2024-03-29 07:54:50 +01:00
<label for="realm_message_content_delete_limit_seconds" class="settings-field-label">
settings: Add `can_delete_any_message_group` setting. Fixes #30717.
2024-08-15 07:29:15 +02:00
{{t "Time limit for deleting messages" }} <i>({{t "does not apply to users who can delete any message" }})</i>
settings: Move message edit settings to "Organization Permissions". The message-editing section of settings is moved from "Organization Settings" to "Organization Permissions", which feels like a more natural place for these settings.
2021-05-25 21:24:12 +02:00
</label>
settings: Add settings_select class to select elements. This commit adds settings_select class to select elements in user and organization settings, such that we can add CSS using this class and not using "select" as selector so that we can easily add a select element in future with different CSS if needed.
2023-02-16 10:57:08 +01:00
<select name="realm_message_content_delete_limit_seconds" id="id_realm_message_content_delete_limit_seconds" class="prop-element bootstrap-focus-style settings_select" data-setting-widget-type="time-limit">
settings: Move message edit settings to "Organization Permissions". The message-editing section of settings is moved from "Organization Settings" to "Organization Permissions", which feels like a more natural place for these settings.
2021-05-25 21:24:12 +02:00
{{#each msg_delete_limit_dropdown_values}}
settings_config: Change time_limit_dropdown_values to a list. This commit changes time_limit_dropdown_values from map to list like we have email_notifications_batching_period_values. This change will help us in further commits for refactoring the message edit and delete settings related code.
2022-09-01 14:19:14 +02:00
<option value="{{value}}">{{text}}</option>
settings: Move message edit settings to "Organization Permissions". The message-editing section of settings is moved from "Organization Settings" to "Organization Permissions", which feels like a more natural place for these settings.
2021-05-25 21:24:12 +02:00
{{/each}}
</select>
settings: Rename dependent-block class to dependent-settings-block. This commit renames dependent-block class to dependent-settings-block and also moves the CSS to app_components.css. This class will now only be used for this particular type of custom inputs and thus we do not need ID in the selectors for applying the CSS.
2022-11-21 11:39:51 +01:00
<div class="dependent-settings-block">
settings: Move custom input div inside the main setting div. This commit moves "dependent-block" div inside the main setting "input-group" div as the custom input is part of that setting only. Also this will help in further refactoring of settings code which will be done in next couple of PRs. There are no changes visually, the space between settings and inputs remain same.
2022-08-31 20:16:01 +02:00
<label for="id_realm_message_content_delete_limit_minutes" class="inline-block realm-time-limit-label">
{{t "Duration deletion is allowed after posting (minutes)" }}:
</label>
<input type="text" id="id_realm_message_content_delete_limit_minutes"
name="realm_message_content_delete_limit_minutes"
settings: Rename admin-realm-time-limit-input class. This commit renames admin-realm-time-limit-input class to time-limit-custom-input such that there is no confusion when it is used for stream settings also.
2023-01-16 10:46:45 +01:00
class="time-limit-custom-input"
settings: Move custom input div inside the main setting div. This commit moves "dependent-block" div inside the main setting "input-group" div as the custom input is part of that setting only. Also this will help in further refactoring of settings code which will be done in next couple of PRs. There are no changes visually, the space between settings and inputs remain same.
2022-08-31 20:16:01 +02:00
autocomplete="off"
value="{{ realm_message_content_delete_limit_minutes }}"/>
</div>
settings: Move message edit settings to "Organization Permissions". The message-editing section of settings is moved from "Organization Settings" to "Organization Permissions", which feels like a more natural place for these settings.
2021-05-25 21:24:12 +02:00
</div>
</div>
</div>
settings: Rearrange settings in "Organization permissions" section. This commit re-arranges the settings in "Organization permissions" section - - A new section "Guests" is added which now contains the guest indicator setting checkbox. - Moved "User identity" and "Guests" sections above "Other permissions" section.
2023-11-23 08:40:42 +01:00
<div id="org-user-identity" class="settings-subsection-parent">
<div class="subsection-header">
organization-permissions: Add help page link for User Identity section. This commit adds the /help link to the User Identity section heading of the Organization Permissions, linking to /help/restrict-name-and- email-changes.
2024-04-03 16:21:52 +02:00
<h3>{{t "User identity" }}
{{> ../help_link_widget link="/help/restrict-name-and-email-changes" }}
</h3>
settings: Rearrange settings in "Organization permissions" section. This commit re-arranges the settings in "Organization permissions" section - - A new section "Guests" is added which now contains the guest indicator setting checkbox. - Moved "User identity" and "Guests" sections above "Other permissions" section.
2023-11-23 08:40:42 +01:00
{{> settings_save_discard_widget section_name="user-identity" }}
</div>
<div class="inline-block organization-permissions-parent">
settings: Add permission to enforce unique names in realm. Previously, users were allowed to signup or change their names to those which already existed in the realm. This commit adds an Organization Permission, that shall enforce users to use unique names while signing up or changing their names. If a same or normalized full name is found in realm, then a validation error is thrown. Fixes #7830.
2024-03-11 20:02:05 +01:00
{{> settings_checkbox
setting_name="realm_require_unique_names"
prefix="id_"
is_checked=realm_require_unique_names
label=admin_settings_label.realm_require_unique_names}}
settings: Rearrange settings in "Organization permissions" section. This commit re-arranges the settings in "Organization permissions" section - - A new section "Guests" is added which now contains the guest indicator setting checkbox. - Moved "User identity" and "Guests" sections above "Other permissions" section.
2023-11-23 08:40:42 +01:00
{{> settings_checkbox
setting_name="realm_name_changes_disabled"
prefix="id_"
is_checked=realm_name_changes_disabled
label=admin_settings_label.realm_name_changes_disabled}}
{{> settings_checkbox
setting_name="realm_email_changes_disabled"
prefix="id_"
is_checked=realm_email_changes_disabled
label=admin_settings_label.realm_email_changes_disabled}}
{{> settings_checkbox
setting_name="realm_avatar_changes_disabled"
prefix="id_"
is_checked=realm_avatar_changes_disabled
label=admin_settings_label.realm_avatar_changes_disabled}}
</div>
</div>
<div id="org-guest-settings" class="settings-subsection-parent">
<div class="subsection-header">
<h3>{{t "Guests" }}</h3>
{{> settings_save_discard_widget section_name="guest-settings" }}
</div>
<div class="inline-block organization-permissions-parent">
{{> settings_checkbox
setting_name="realm_enable_guest_user_indicator"
prefix="id_"
is_checked=realm_enable_guest_user_indicator
label=admin_settings_label.realm_enable_guest_user_indicator}}
settings: Add support to change user-access setting in development. This commit updates the backend code to allow changing can_access_all_users_group setting in development environment and also adds a dropdown in webapp UI which is only shown in development environment.
2023-11-23 10:14:35 +01:00
settings: Fix width of can-access-all-users-group widget container. This commit moves dropdown widget for "can_access_all_users_group" setting inside ".organization-permissions-parent" element which makes it consistent with other settings and also reduces the width of its container which is important in further commits to show the tooltip about plan change on this setting correctly.
2023-11-28 10:07:51 +01:00
{{> ../dropdown_widget_with_label
widget_name="realm_can_access_all_users_group"
settings: Update the label for can_access_all_users_group setting.
2023-12-10 08:59:11 +01:00
label=(t 'Who can view all other users in the organization')
settings: Add help link for "can_access_all_users_group" setting.
2023-12-11 11:27:02 +01:00
value_type="number"
help_link="/help/guest-users#configure-whether-guests-can-see-all-other-users"}}
settings: Fix width of can-access-all-users-group widget container. This commit moves dropdown widget for "can_access_all_users_group" setting inside ".organization-permissions-parent" element which makes it consistent with other settings and also reduces the width of its container which is important in further commits to show the tooltip about plan change on this setting correctly.
2023-11-28 10:07:51 +01:00
</div>
settings: Rearrange settings in "Organization permissions" section. This commit re-arranges the settings in "Organization permissions" section - - A new section "Guests" is added which now contains the guest indicator setting checkbox. - Moved "User identity" and "Guests" sections above "Other permissions" section.
2023-11-23 08:40:42 +01:00
</div>
settings: Rename "org-subsection-parent" class to "settings-subsection-parent". This commit renames the "org-subsection-parent" class used for organization settings subsections to "settings-subsection-parent" such that we can use same for the stream settings and avoid duplicating code for handling save-discard widget which will be added in future.
2022-11-03 13:18:42 +01:00
<div id="org-other-permissions" class="settings-subsection-parent">
settings: Reorganize options/sections in `Organization Permissions`. As a consequence of too many options in the bottom `Other permissions` subsection, the `Save` button could end up too far up from the bottom, such that it might appear offscreen on low-height laptops. We fix this by reorganizing the settings in a way that is both more intuitive and also ensures that none of the subsections are too tall. Fixes: #14274.
2020-03-23 21:51:27 +01:00
<div class="subsection-header">
<h3>{{t "Other permissions" }}</h3>
{{> settings_save_discard_widget section_name="other-permissions" }}
</div>
<div class="m-10 inline-block organization-permissions-parent">
org permissions: Restructure org-permissions-admin template. We restructured template to make org-permissions-template have more separated subsections and so that we can easily apply event handlers and selectors to their corresponding subsections (there will be no change in UI). (This is similar to 8b54b08)
2018-03-20 23:18:34 +01:00
<div class="input-group">
settings: Add bottom margin to label elements. This commit adds bottom margin to label elements of settings inputs in personal, organization, stream and group settings using the recently added "settings-field-label" class. Most of the settings are dropdown settings, so the label for them already had a margin as they use "dropdown-title" class.
2024-03-29 11:20:36 +01:00
<label for="realm_bot_creation_policy" class="settings-field-label">{{t "Who can add bots" }}</label>
settings: Add settings_select class to select elements. This commit adds settings_select class to select elements in user and organization settings, such that we can add CSS using this class and not using "select" as selector so that we can easily add a select element in future with different CSS if needed.
2023-02-16 10:57:08 +01:00
<select name="realm_bot_creation_policy" class="setting-widget prop-element settings_select bootstrap-focus-style" id="id_realm_bot_creation_policy" data-setting-widget-type="number">
settings_org: Extract the "options" code as template. This is a preliminary commit for upcoming change where we will use "bot_creation_policy_values" like approach for many other settings where dropdown represents the only single setting of integer type.
2020-01-22 19:01:51 +01:00
{{> dropdown_options_widget option_values=bot_creation_policy_values}}
org permissions: Restructure org-permissions-admin template. We restructured template to make org-permissions-template have more separated subsections and so that we can easily apply event handlers and selectors to their corresponding subsections (there will be no change in UI). (This is similar to 8b54b08)
2018-03-20 23:18:34 +01:00
</select>
</div>
org settings: Add setting to prevent users from adding bots. Fixes: #7908.
2018-01-29 16:10:54 +01:00
settings: Use new UI for can_add_custom_emoji_group setting.
2024-10-29 11:29:01 +01:00
{{> group_setting_value_pill_input
setting_name="realm_can_add_custom_emoji_group"
label=(t 'Who can add custom emoji')}}
Split out Organization Permissions page.
2017-05-18 14:06:57 +02:00
</div>
settings: Reorder options in organization-permissions-admin.handlebars. Also adds <hr>'s to separate the options into sections.
2017-07-12 23:32:14 +02:00
</div>
Split out Organization Permissions page.
2017-05-18 14:06:57 +02:00
</form>
</div>