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

76 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
help: Update "private message" -> "direct message" term. Updates all help center pages to match new DM term in Zulip UI.
2023-02-10 08:04:36 +01:00
all direct messages and all streams without a specific policy.
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 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
web: Save a needless 301 redirect from /plans to /plans/.
2023-03-23 03:53:14 +01:00
Cloud Standard and Zulip Cloud Plus [plans](https://zulip.com/plans/),
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
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.
help: Rename 'select-stream-view...' include instructions.
2024-04-30 21:57:47 +02:00
{!select-channel-view-general.md!}
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
help: Update help docs for changing stream permission settings. We changed the stream permission settings UI for setting widgets to always be present in "General" section instead of a modal. This commit updates the help center documentation to be consistent with the new UI. Fixes #19519.
2022-12-06 09:24:04 +01:00
1. Under **Stream permissions**, configure the
help_docs: Update `message-retention-policy` help doc. Uses new `select-stream-view-general.md` for instructions. Also, updates the text for locating the button/icon.
2022-03-21 13:13:51 +01:00
**Message retention period**.
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
{!save-changes.md!}
{end_tabs}
bots: Refer to notification bot messages as automated notices. Updates in-app and documentation references to automated messages sent by the notification bot as automated notices (or automated messages where more appropriate/clear), instead of notifications. Also, makes some small related revisions / general clean ups to `resolve-a-topic.md`. Fixes #22188.
2022-07-28 15:38:32 +02:00
{!automated-notice-stream-event.md!}
help_docs: Document auto-notifications for general stream updates. Adds a note about auto-notification messages that are sent when these general settings are changed for a stream: name, description, access and posting permissions, and message retention.
2022-03-24 21:18:31 +01:00
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
help: Rename edit-or-delete-a-message.md and update links.
2023-07-19 01:39:18 +02:00
documentation](/help/delete-a-message#delete-a-message-completely) for
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
more details on precisely how message deletion works in Zulip.
## Related articles
help: Rename edit-or-delete-a-message.md and update links.
2023-07-19 01:39:18 +02:00
* [Edit a message](/help/edit-a-message)
* [Delete a message](/help/delete-a-message)
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
* [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)