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.
2.3 KiB
Message retention policy
{!owner-only.md!}
By default, Zulip stores messages indefinitely, allowing full-text search of your complete history.
Zulip supports configuring both a global organization-level message retention policy, as well as retention policies for individual channels. These policies control how many days a message is stored before being automatically deleted (the default being forever). Zulip's system supports:
- Setting an organization-level retention policy, which applies to all direct messages and all channels without a specific policy.
- Setting a retention policy for individual channels, which overrides the organization-level policy for that channel. This can be used to just delete messages on specific channels, to only retain messages forever on specific channels, or just to have a different retention period.
In Zulip Cloud, message retention policies are available on the Zulip Cloud Standard and Zulip Cloud Plus plans, as well as for the hundreds of communities with sponsored Cloud Standard hosting.
Configure message retention policy for organization
{start_tabs}
{settings_tab|organization-settings}
- Under Message retention period, configure Message retention period.
{!save-changes.md!}
{end_tabs}
Configure message retention policy for individual channels
{start_tabs}
{relative|channel|all}
- Select a channel.
{!select-channel-view-general-advanced.md!}
- Under Administrative permissions, configure the Message retention period.
{!save-changes.md!}
{end_tabs}
{!automated-notice-channel-event.md!}
Important details
- Retention policies are processed in a daily job; so changes in the policy won't have any effect until the next time the daily job runs.
- Deleted messages are preserved temporarily in a special archive. So if you discover a misconfiguration accidentally deleted content you meant to preserve, contact Zulip support promptly for assistance with restoration. See the deletion documentation for more details on precisely how message deletion works in Zulip.