Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/templates/zerver/help/message-retention-policy.md

42 lines
1.7 KiB
Markdown
Raw Normal View History

docs: Document message retention policies. We've completed the production performance testing that had been blocking us from advertising this feature, so we're declaring the feature implemented by documenting it. As of this commit, you need to edit fields using `manage.py shell` to configure it and manually configure the cron job, but those should be addressed in the next few days. Fixes #106.
2020-05-04 08:38:54 +02:00
# Message retention policy (beta)
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
streams. These policies control how many days a message is stored
before being automatically deleted (the default being forever).
Zulip's system supports:
* Setting a retention policy for individual streams, to just delete
messages on those specific streams.
* Setting an organization-level policy, and a "forever" policy for
specific streams, to preserve messages indefinitely on those
streams, while automatically deleting both PMs and messages sent to
other streams.
In Zulip Cloud, message retention policies are available on the Zulip
Cloud Standard and Zulip Cloud Plus [plans](https://zulip.com/plans),
as well as for the hundreds of communities with sponsored Cloud
docs: Replace support@zulipchat.com with support@zulip.com. The new address is cleaner and shorter.
2020-05-28 02:00:13 +02:00
Standard hosting. Contact support@zulip.com if you're on one of
docs: Document message retention policies. We've completed the production performance testing that had been blocking us from advertising this feature, so we're declaring the feature implemented by documenting it. As of this commit, you need to edit fields using `manage.py shell` to configure it and manually configure the cron job, but those should be addressed in the next few days. Fixes #106.
2020-05-04 08:38:54 +02:00
these plans and would like to enable it.
## 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
docs: Fix typo in message-retention-policy.md.
2020-05-06 15:00:16 +02:00
meant to preserve, contact Zulip support promptly for assistance with
docs: Document message retention policies. We've completed the production performance testing that had been blocking us from advertising this feature, so we're declaring the feature implemented by documenting it. As of this commit, you need to edit fields using `manage.py shell` to configure it and manually configure the cron job, but those should be addressed in the next few days. Fixes #106.
2020-05-04 08:38:54 +02:00
restoration. See the [deletion
documentation](/help/edit-or-delete-a-message#how-deletion-works) for
more details on precisely how message deletion works in Zulip.
## Related articles
* [Edit or delete a message](/help/edit-or-delete-a-message)
* [Delete a topic](/help/delete-a-topic)
* [Delete a stream](/help/delete-a-stream)