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

73 lines
2.3 KiB
Markdown
Raw Normal View History

docs: Remove "beta" mark from message-retention-policy.md. The retention policy has been sufficiently well tested at this point to consider it stable.
2021-03-25 20:12:50 +01:00
# Message retention policy
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
realm: Allow only owners to set message retention policy for a realm. This commits adds restriction on admins to set message retention policy. We now only allow only organization owners to set message retention policy. Dropdown for changing retention policy is disabled in UI for admins also.
2020-06-11 21:16:53 +02:00
{!owner-only.md!}
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
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:
docs: Update documentation for retention policy UI. This still needs a follow-up PR to use our standard systems for explaining how to access these features.
2020-06-19 02:17:07 +02:00
* Setting an organization-level retention policy, which applies to
all private messages and all streams without a specific policy.
* Setting a retention policy for individual streams, which overrides
the organization-level policy for that stream. This can be used to
just delete messages on specific streams, to only retain messages
forever on specific streams, or just to have a different retention
period.
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
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: Update documentation for retention policy UI. This still needs a follow-up PR to use our standard systems for explaining how to access these features.
2020-06-19 02:17:07 +02:00
Standard hosting.
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
docs: Add steps for configuring message retention policy in the docs. This commits adds the steps for configuring message retention policy for an organization and for individual streams in message retention policy docs. Fixes #15495.
2020-07-06 21:28:35 +02:00
### Configure message retention policy for organization
{start_tabs}
{settings_tab|organization-settings}
4. Under **Message retention**, configure **Message retention period**.
{!save-changes.md!}
{end_tabs}
### Configure message retention policy for individual streams
{start_tabs}
{relative|stream|all}
1. Select a stream.
1. On the right, click **[Change]** next to the description of the stream
permissions.
1. Under **Message retention for stream**, configure **Message retention period**.
{!save-changes.md!}
{end_tabs}
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
## 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)
streams: Use "archive stream" phrasing instead of "delete stream". The previous phrasing was misleading in relation to what the action actually does.
2021-03-31 16:15:24 +02:00
* [Archive a stream](/help/archive-a-stream)