Compliance Export updates #7719
Conversation
|
Newest code from mattermost has been published to preview environment for Git SHA 6cb981e |
source/comply/compliance-export.rst
Outdated
|
|
||
| Compliance exports are produced from the System Console, containing all messages including: | ||
| While Mattermost stores all message history by default, system admins can specify a :doc:`custom data retention policy </comply/data-retention-policy>` for how long messages and file uploads are kept in Mattermost channels and direct messages. |
There was a problem hiding this comment.
Data retention is something different from compliance exports, though... I wonder if we're confusing the two by having this here?
source/comply/compliance-export.rst
Outdated
|
|
||
| - Messages sent in direct message channels | ||
| - File uploads | ||
| - Posts from plugins | ||
| - Posts from bots/webhooks | ||
|
|
||
| Exports include information on channel member history at the time the message was posted. | ||
| Exports include information on channel member history at the time the message was posted. | ||
|
|
||
| - Entries for deleted messages and files are included in CSV and Actiance reports. The deleted content is included in the compliance export. | ||
| - Global Relay reports include file deletion entries but message deletion entries are excluded. |
There was a problem hiding this comment.
We can remove this -- all export formats include deleted message info now.
source/comply/compliance-export.rst
Outdated
| When the daily compliance export job is finished, a parent directory is created named based on when the export was started and the ``startTimestamp`` and ``endTimestamp`` of the export, e.g, ``compliance-export-2024-08-13-05h08m-1723105062492-1723109100075``. That parent directory contains 1 zip file for each batch, named based on the batch number and the start and end timestamps of the messages in that batch, e.g, ``batch001-1723105062492-1723106622163.zip``. Each zip file contains the same information available in previous Mattermost server releases. | ||
|
|
||
| Working from the same example above, the directory would look like this: | ||
|
|
||
| .. code-block:: bash | ||
|
|
||
| compliance-export-2024-08-13-05h08m-1723105062492-1723109100075 | ||
| ├── batch001-1723105062492-1723106622163.zip | ||
| ├── batch002-1723106622163-1723108196005.zip | ||
| └── batch003-1723108196005-1723109100075.zip | ||
|
|
||
| And each batch would look like this: | ||
|
|
||
| .. code-block:: bash | ||
|
|
||
| batch001-1723105062492-1723106622163.zip | ||
| ├── 20240808 | ||
| └── actiance_export.xml |
There was a problem hiding this comment.
This isn't relevant for Global Relay -- the results will be emailed to the recipient, at least one email per channel (or >1 email if the channel export is too large for one email).
We don't need to explain the format of the email, I think.
Co-authored-by: Christopher Poile <[email protected]>
|
Newest code from mattermost has been published to preview environment for Git SHA a7b0a7c |
|
Newest code from mattermost has been published to preview environment for Git SHA f09065b |
|
@cpoile - Can I get your help updating this docs PR to address mattermost/mattermost#28805, please? |
|
@cwarnermm Sure: #7728 |
cwarnermm
added
3: Reviews Complete
Documentation for: mattermost/mattermost#29789