You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: source/administration/changelog.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ Also see [changelog in progress](http://bit.ly/2nK3cVf) for the next release.
8
8
9
9
- **v5.22.1, released 2020-04-23**
10
10
- Fixed an issue where Amazon S3 file storage with IAM credentials failed due to a bug in the ``minio-go`` library. [MM-24388](https://mattermost.atlassian.net/browse/MM-24388)
Copy file name to clipboardExpand all lines: source/administration/compliance.rst
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ Enabling Compliance Reporting
21
21
22
22
After purchasing and installing a license key for Enterprise Edition E20:
23
23
24
-
1. Go to **System Console > Compliance > Compliance Monitoring** (or **System Console** > **General** > **Compliance** > **Enable Compliance** in versions prior to 5.12) and set the **Enable Compliance Reporting** value to ``true``.
24
+
1. Go to **System Console > Compliance > Compliance Monitoring** (or **System Console > General > Compliance > Enable Compliance** in versions prior to 5.12) and set the **Enable Compliance Reporting** value to **true**.
25
25
2. (Optional) In **Compliance Report Directory** specify the directory in which to place completed compliance reports. Defaults to ``./data/`` if left blank.
26
26
3. Click **Save**.
27
27
@@ -32,23 +32,23 @@ Turn on Daily Compliance Reports
32
32
33
33
After enabling compliance reporting:
34
34
35
-
1. Go to **System Console > Compliance > Compliance Monitoring** (or **System Console** > **General** > **Compliance** > **Enable Daily Report** in versions prior to 5.12) and set the **Enable Daily Report** value to ``true``.
35
+
1. Go to **System Console > Compliance > Compliance Monitoring** (or **System Console > General > Compliance > Enable Daily Report** in versions prior to 5.12) and set the **Enable Daily Report** value to **true**.
36
36
2. Click **Save**.
37
37
38
-
Your system will now export all new messages posted within a 24-hour period as a .csv file to the location specified in **Compliance Report Directory**. This feature can be used in conjunction with centralized compliance reporting systems that move.
38
+
Your system will now export all new messages posted within a 24-hour period as a ``.csv`` file to the location specified in **Compliance Report Directory**. This feature can be used in conjunction with centralized compliance reporting systems that move.
39
39
40
40
Run Compliance Reports
41
41
======================
42
42
43
43
Compliance Reports are exports of all messages in Mattermost that match the report criteria. To run a report:
44
44
45
-
1. Go to **System Console** > **Compliance Monitoring** (or **System Console > Compliance > Compliance Monitoring** in versions prior to 5.12).
45
+
1. Go to **System Console > > Compliance > Compliance Monitoring** (or **System Console > Compliance > Compliance Monitoring** in versions prior to 5.12).
46
46
2. Fill in the following criteria:
47
47
48
-
- **Job Name:** Name the compliance report you are about to run (e.g., "HR Audit 455").
49
-
- **From:** Start Date for search in YYYY-MM-DD format (e.g., "2016-03-11").
50
-
- **To:** End Date of search in YYYY-MM-DD format (e.g., "2016-05-11").
51
-
- **Emails:** Commaseparated list of email addresses of users whose posted messages you want to search (e.g., ``[email protected], [email protected]``).
48
+
- **Job Name:** Name the compliance report you are about to run (e.g. "HR Audit 455").
49
+
- **From:** Start Date for search in YYYY-MM-DD format (e.g. "2016-03-11").
50
+
- **To:** End Date of search in YYYY-MM-DD format (e.g. "2016-05-11").
51
+
- **Emails:** Comma-separated list of email addresses of users whose posted messages you want to search (e.g. ``[email protected], [email protected]``).
52
52
- **Keywords:** Indicate the words that would be contained in a message for it to be included in the Compliance Report results.
53
53
3. Click **Run Compliance Report**.
54
54
@@ -62,7 +62,7 @@ The report will be queued in the display below the fields described above. The p
62
62
- **Requested by:** Email of person requesting the report.
63
63
- **Params:** Parameters of the compliance report request.
64
64
65
-
Each Compliance Report includes a **Download** link which downloads a compressed file named ``adhoc-[UNIQUE_ID].zip``. Inside the file is ``meta.json``, which includes the parameters of the search executed and ``posts.csv`` which includes the contents of messages found by the request.
65
+
Each compliance report includes a **Download** link which downloads a compressed file named ``adhoc-[UNIQUE_ID].zip``. Inside the file is ``meta.json``, which includes the parameters of the search executed and ``posts.csv`` which includes the contents of messages found by the request.
66
66
67
67
Compliance query definition stored in ``meta.json`` file
Copy file name to clipboardExpand all lines: source/administration/migrating.rst
+10-2Lines changed: 10 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -110,7 +110,6 @@ Slack offers two ways to `export your data from their product <https://get.slack
110
110
111
111
2. You can request a "Corporate Export" from Slack directly to get a larger export including private channels, direct, and group messages.
112
112
113
-
Both exports from Slack use the same processes when importing into Mattermost.
114
113
115
114
.. note:: As a proprietary SaaS service, Slack is able to change its export format quickly and without notice. If you encounter issues not mentioned in the documentation below, please alert the product team by `filing an issue <https://www.mattermost.org/filing-issues/>`__.
116
115
@@ -170,7 +169,7 @@ The following limitations are present when importing from Slack:
170
169
Migrating from Slack using the Mattermost Web App
171
170
`````````````````````````````````````````````````
172
171
173
-
.. note:: For larger imports, particularly those where you have used the `slack-advanced-exporter tool` to add Slack post attachments to the archive or the Corporate Export file, it is recommended to import the Slack data using the `CLI <https://docs.mattermost.com/administration/migrating.html#migrating-from-slack-using-the-mattermost-cli>`__.
172
+
.. note:: For larger imports, particularly those where you have used the `slack-advanced-exporter tool` to add Slack post attachments to the archive or the Corporate Export file, it is recommended to import the Slack data using the `mmetl tool and bulk loading tool <https://docs.mattermost.com/administration/migrating.html#migrating-from-slack-using-the-mattermost-mmetl-tool-and-bulk-import>`__.
174
173
175
174
1. Generate a Slack export file from **Slack > Administration > Workspace Settings > Import/Export Data > Export > Start Export**. Alternatively, use the Slack Corporate Export file after receiving it from Slack.
176
175
@@ -190,7 +189,16 @@ Migrating from Slack Using the Mattermost CLI
190
189
191
190
.. note:: To run the CLI command, you must be in the directory that contains the Mattermost installation. On a default installation of Mattermost, the directory is ``/opt/mattermost/``. Also, if you followed our `installation process <../guides/administrator.html#installing-mattermost>`__, you must run the command as the user *mattermost*. The executable is in the ``bin`` subdirectory and is called ``mattermost``.
192
191
192
+
Migrating from Slack Using the Mattermost mmetl Tool and Bulk Import
.. note:: This method is the recommended way to import Slack's corporate export file.
193
195
196
+
1. Use the `slack-advanced-exporter <https://github.com/grundleborg/slack-advanced-exporter>`_ to download attachments and add users' email addresses to your Slack corporate export file.
197
+
198
+
2. Use the `mmetl tool <https://github.com/mattermost/mmetl>`_ to transform Slack's corporate export file into the ``jsonl`` format required by the bulk import tool.
199
+
200
+
3. Bulk load the files using the steps provided in the `bulk loading documentation <https://docs.mattermost.com/deployment/bulk-loading.html#bulk-loading-data>`_.
Plugins in the Marketplace are labeled to make it easier for administrators to choose plugins that fit their company's security and risk policies if they do not allow for community plugins to be used.
27
+
28
+
**Community Plugins**
29
+
30
+
Plugins identified as "Community" are produced by the open-source community or partners and the features/roadmap are not controlled directly by Mattermost. Prior to being listed on the Plugin Marketplace, they are reviewed by the Mattermost development team and code-signed to ensure the code Mattermost reviewed, is delivered. Mattermost does not directly support these plugins in production environments.
31
+
32
+
**Beta Plugins**
33
+
34
+
Plugins may be labeled as "Beta" if they are released to the Plugin Marketplace early for customer previews. We do not recommend running Beta plugins on production servers.
Copy file name to clipboardExpand all lines: source/administration/upgrade.rst
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,6 +16,9 @@ Read these instructions carefully from start to finish. Make sure that you under
16
16
17
17
.. important::
18
18
Review the :doc:`important-upgrade-notes` to make sure you are aware of any actions you need to take before or after upgrading from your particular version.
19
+
20
+
.. important::
21
+
If you're upgrading from a version prior to v5.0 be sure to also modify your service file to work with the binary changes introduced with 5.0. Your execution directory should point to the Mattermost base directory (i.e. `/opt/mattermost`) and your binary should point to the `mattermost` binary (i.e. `/opt/mattermost/bin/mattermost`).
19
22
20
23
You should gather the following information before starting the upgrade:
Copy file name to clipboardExpand all lines: source/help/messaging/sending-messages.rst
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,10 @@ Write a message by typing into the text input box, then press ENTER to send it.
13
13
Replying to Messages
14
14
---------------------
15
15
16
-
Click the reply link (arrow icon that appears when hovering over a message) next to any message. This keeps conversations organized in threads. Replies are indented slightly in the center pane to indicate that they are child messages of a parent message.
16
+
Hover over any message and click the reply link (arrow icon |replyarrow|). This organizes the conversation into a thread. Replies are indented slightly in the center pane to indicate that they are child messages of a parent message.
Clicking the reply link will open a sidebar on the right-hand side. To expand the right-hand sidebar to its full width, click the expand/shrink icon with two arrows at the top of the sidebar. To shrink the right-hand sidebar to its original width, click the same expand/shrink icon.
Copy file name to clipboardExpand all lines: source/help/settings/custom-emoji.rst
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,8 @@
2
2
Custom Emoji
3
3
------------------
4
4
5
+
**Note:** If you cannot see the **Custom Emoji** option in the menu, then your System Administrator may have restricted access to certain users. Contact your System Administrator for help.
6
+
5
7
Settings for Custom Emoji are accessible from the **Main Menu** by clicking the hamburger menu at the top of the channels sidebar. Clicking **Custom Emoji** opens a page where you can view existing Custom Emojis and create new ones.
6
8
7
9
To create a Custom Emoji:
@@ -16,5 +18,3 @@ To create a Custom Emoji:
16
18
Small, square pictures work best when selecting an image. The file can be any JPG, GIF, or PNG.
17
19
18
20
After saving, your emoji will show up in the list of Custom Emoji. To add your Custom Emoji to a message, simply type ":" followed by your emoji name to bring it up in the emoji autocomplete. Other users on the site will also be able to see your emoji in the autocomplete, and will be able to use it in their own messages.
19
-
20
-
Note: If you cannot see the **Custom Emoji** option in the menu, then your System Administrator may have restricted access to certain users. Contact your System Administrator for help.
0 commit comments