+})
Topics demonstrated:
@@ -37,7 +38,7 @@ Topics demonstrated:
The [JIRA plugin for Mattermost](https://github.com/mattermost/mattermost-plugin-jira) creates a webhook that your JIRA server can use to post messages to Mattermost when issues are created:
-
+})
Topics demonstrated:
@@ -59,7 +60,7 @@ Topics demonstrated:
The [Memes plugin for Mattermost](https://github.com/mattermost/mattermost-plugin-memes) creates a slash command that can be used to create dank memes:
-
+})
Topics demonstrated:
diff --git a/docs/main/administration-guide/comply/embedded-json-audit-log-schema.mdx b/docs/main/administration-guide/comply/embedded-json-audit-log-schema.mdx
index 4a2e7a97b8c..99e6839bc3a 100644
--- a/docs/main/administration-guide/comply/embedded-json-audit-log-schema.mdx
+++ b/docs/main/administration-guide/comply/embedded-json-audit-log-schema.mdx
@@ -1,6 +1,8 @@
---
title: "Audit log JSON schema"
---
+import useBaseUrl from '@docusaurus/useBaseUrl';
+
-
-
- Write Timeout | Temporarily adjust this value based on import file speed and network path to enable the file to upload without timeouts. | | Start with a value of 3600 and adjust if needed. | +
- Write Timeout | Temporarily adjust this value based on import file speed and network path to enable the file to upload without timeouts. | | Start with a value of 3600 and adjust if needed. |
-
Following a successful import, we strongly recommend reverting this setting to its initial or previous value. |
@@ -214,14 +216,14 @@ Finally, it's time to take our export from the source server and use it as an im
-
-
- Read Timeout | Temporarily adjust this value based on import file speed and network path to enable the file to upload without timeouts. | | Start with a value of 3600 and adjust if needed. | +
- Read Timeout | Temporarily adjust this value based on import file speed and network path to enable the file to upload without timeouts. | | Start with a value of 3600 and adjust if needed. |
-
Following a successful import, we strongly recommend reverting this setting to its initial or previous value. |
role_updated WebSocket events are scoped to the affected team/channel instead of broadcasting globally, improving performance and reducing unnecessary network traffic. No manual action is required from administrators as the migration runs automatically during the upgrade. No downtime is expected, and no special planning is needed for the upgrade as the migration can run during normal operations. All installations are affected by this change, but the impact is minimal since the roles table is small with well under 10k rows even on large installations. The upgrade includes automatic database migrations to add a schemeid column to the roles table for efficient role-scheme lookups. The migrations use PostgreSQL's non-blocking techniques: first adding the column with a brief ACCESS EXCLUSIVE lock (catalog-only operation), then backfilling existing data with a ROW EXCLUSIVE lock, and finally creating an index concurrently with a SHARE UPDATE EXCLUSIVE lock that doesn't block other operations. The roles table size is bounded and unaffected by posts, reactions, or other high-volume data. The migrations are fully backwards-compatible.
v11.7.6 migration removes orphaned rows from the threadmemberships table — specifically, rows where the associated user is no longer a member of the channel that the thread belongs to. The cleanup is performed via a filtered DELETE using a three-way join across threadmemberships, threads, and channelmembers. No schema objects (tables, columns, or indexes) are added or removed; only data rows are affected. Note for large instances: this migration issues a single unbatched delete that scans the entirety of threadmemberships with a join against threads and channelmembers. On databases with tens of millions of rows or significant historical channel-membership churn, this query may run for an extended period, block autovacuum on threadmemberships, increase WAL pressure, and contribute to replication lag. Administrators of large deployments should test execution time on a representative dataset before upgrading and consider scheduling the upgrade during a low-traffic window. The down migration contains no rollback SQL because the deleted rows cannot be recovered; this migration is irreversible. The migrations are fully backwards-compatible and no database downtime is expected for this upgrade. The SQL queries included are:
-- Drop ThreadMembership rows whose user is no longer a member of the thread's channel.
@@ -683,7 +685,7 @@ DELETE FROM threadmemberships WHERE (postid, userid) IN (
System Console statistics now perform faster on PostgreSQL. The MaxUsersForStatistics configuration setting now only disables the User counts with posts chart, while all other stats remain unaffected. The other stats remain unaffected because that configuration value is no longer needed to disable the other queries since they are always fast now. Post and file counts update daily, so they may not always reflect real-time data. Advanced stats, such as line charts and plugin data, are now hidden until clicked, reducing load time. No performance improvements apply to MySQL since it's scheduled for full deprecation in v11. We recommend migrating to PostgreSQL for better performance and long-term support. Migration times: On a system with 12M posts, and 1M fileinfo entries, the migration takes 15s, but could take several minutes depending on the server's table sizes and database specs. This migration is non-locking. Note that there is no migration for MySQL deployments because this optimization is only applicable for PostgreSQL. Below are the SQL queries included in the schema changes:
CREATE MATERIALIZED VIEW IF NOT EXISTS posts_by_team_day asSELECT to_timestamp(p.createat/1000)::date as day, COUNT(*) as num, teamidFROM posts p JOIN channels c on p.channelid=c.idGROUP BY day, c.teamid;CREATE MATERIALIZED VIEW IF NOT EXISTS bot_posts_by_team_day asSELECT to_timestamp(p.createat/1000)::date as day, COUNT(*) as num, teamidFROM posts pJOIN Bots b ON p.UserId = b.UseridJOIN channels c on p.channelid=c.idGROUP BY day, c.teamid;CREATE MATERIALIZED VIEW IF NOT EXISTS file_stats asSELECT COUNT(*) as num, COALESCE(SUM(Size), 0) as usageFROM fileinfoWHERE DeleteAt = 0;As part of the Property System Architecture feature, Mattermost v10.5 is going to run a set of migrations to add new tables to the schema. This migration only creates new tables and indexes, so there is no impact on preexisting data.
New tables PropertyGroups, PropertyFields and PropertyValues are going to be created.
In the case of PostgreSQL, a new enum type property_field_type is going to be created, to be used in the Type column of the PropertyFields table.
The PropertyFields and PropertyValues tables have a unique constraint that will generate an index in MySQL, and in the case of PostgreSQL, they directly use a UNIQUE INDEX to enforce this constraint.
A new index idx_propertyvalues_targetid_groupid will be created for the PropertyValues table.
The migration is only creating new tables with no data. The migration is backwards-compatible, and a previous version of Mattermost can run with the new schema changes. No table locks or existing operations on the table are impacted by this upgrade. Zero downtime is possible when upgrading to this release.
Below are the SQL queries included in the schema changes:
MySQL:
CREATE TABLE IF NOT EXISTS PropertyGroups ( ID varchar(26) PRIMARY KEY, Name varchar(64) NOT NULL, UNIQUE(Name));CREATE TABLE IF NOT EXISTS PropertyFields ( ID varchar(26) PRIMARY KEY, GroupID varchar(26) NOT NULL, Name varchar(255) NOT NULL, Type enum('text', 'select', 'multiselect', 'date', 'user', 'multiuser'), Attrs json, TargetID varchar(255), TargetType varchar(255), CreateAt bigint(20), UpdateAt bigint(20), DeleteAt bigint(20), UNIQUE(GroupID, TargetID, Name, DeleteAt));CREATE TABLE IF NOT EXISTS PropertyValues ( ID varchar(26) PRIMARY KEY, TargetID varchar(255) NOT NULL, TargetType varchar(255) NOT NULL, GroupID varchar(26) NOT NULL, FieldID varchar(26) NOT NULL, Value json, CreateAt bigint(20), UpdateAt bigint(20), DeleteAt bigint(20), UNIQUE(GroupID, TargetID, FieldID, DeleteAt));SET @preparedStatement = (SELECT IF( ( SELECT COUNT(*) FROM INFORMATION_SCHEMA.STATISTICS WHERE table_name = 'PropertyValues' AND table_schema = DATABASE() AND index_name = 'idx_propertyvalues_targetid_groupid' ) > 0, 'SELECT 1', 'CREATE INDEX idx_propertyvalues_targetid_groupid ON PropertyValues (TargetID, GroupID);'));PREPARE createIndexIfNotExists FROM @preparedStatement;EXECUTE createIndexIfNotExists;DEALLOCATE PREPARE createIndexIfNotExists;PostgreSQL:
CREATE TABLE IF NOT EXISTS PropertyGroups ( ID varchar(26) PRIMARY KEY, Name varchar(64) NOT NULL, UNIQUE(Name));DOBEGIN IF NOT EXISTS (SELECT * FROM pg_type typ INNER JOIN pg_namespace nsp ON nsp.oid = typ.typnamespace WHERE nsp.nspname = current_schema() AND typ.typname = 'property_field_type') THEN CREATE TYPE property_field_type AS ENUM ( 'text', 'select', 'multiselect', 'date', 'user', 'multiuser' ); END IF;END;LANGUAGE plpgsql;CREATE TABLE IF NOT EXISTS PropertyFields ( ID varchar(26) PRIMARY KEY, GroupID varchar(26) NOT NULL, Name varchar(255) NOT NULL, Type property_field_type, Attrs jsonb, TargetID varchar(255), TargetType varchar(255), CreateAt bigint NOT NULL, UpdateAt bigint NOT NULL, DeleteAt bigint NOT NULL);CREATE UNIQUE INDEX IF NOT EXISTS idx_propertyfields_unique ON PropertyFields (GroupID, TargetID, Name) WHERE DeleteAt = 0;CREATE TABLE IF NOT EXISTS PropertyValues ( ID varchar(26) PRIMARY KEY, TargetID varchar(255) NOT NULL, TargetType varchar(255) NOT NULL, GroupID varchar(26) NOT NULL, FieldID varchar(26) NOT NULL, Value jsonb NOT NULL, CreateAt bigint NOT NULL, UpdateAt bigint NOT NULL, DeleteAt bigint NOT NULL);CREATE UNIQUE INDEX IF NOT EXISTS idx_propertyvalues_unique ON PropertyValues (GroupID, TargetID, FieldID) WHERE DeleteAt = 0;CREATE INDEX IF NOT EXISTS idx_propertyvalues_targetid_groupid ON PropertyValues (TargetID, GroupID); ``ElasticsearchSettings.Backend has been | added to differentiate between Elasticsearch and OpenSearch. The default value is elasticsearch which breaks support for AWS Elasticsearch v7.10.x | since the official v8 client only works from Elasticsearch v7.11+ versions. | | .. note:: | | - For AWS customers on OpenSearch, you must modify Mattermost configuration from elasticsearch to opensearch and disable compatibility mode. | See the OpenSearch documentation for details on upgrading. | - After upgrading the Mattermost server, use mmctl or edit the config manually, | then restart the Mattermost server. | - If you are using OpenSearch, you must set the backend to opensearch. Otherwise Mattermost will not work. | | If you are using Elasticsearch v8, be sure to set action.destructive_requires_name to false in elasticsearch.yml to allow for wildcard operations to | work. |ElasticsearchSettings.Backend has been | added to differentiate between Elasticsearch and OpenSearch. The default value is elasticsearch which breaks support for AWS Elasticsearch v7.10.x | since the official v8 client only works from Elasticsearch v7.11+ versions. | | .. note:: | | - For AWS customers on OpenSearch, you must modify Mattermost configuration from elasticsearch to opensearch and disable compatibility mode. | See the OpenSearch documentation for details on upgrading. | - After upgrading the Mattermost server, use mmctl or edit the config manually, | then restart the Mattermost server. | - If you are using OpenSearch, you must set the backend to opensearch. Otherwise Mattermost will not work. | | If you are using Elasticsearch v8, be sure to set action.destructive_requires_name to false in elasticsearch.yml to allow for wildcard operations to | work. |model.CommandArgs.Session.ServiceSettings.AllowCorsFrom | configuration setting. Also ensure that | the siteURL is set correctly. |ServiceSettings.AllowCorsFrom | configuration setting. Also ensure that | the siteURL is set correctly. |mattermost-server, mattermost-webapp and mmctl. Developers should read the updated Developer Guide for details.ServiceSettings.AllowCorsFrom | configuration setting. Also ensure that | the siteURL is set correctly. |ServiceSettings.AllowCorsFrom | configuration setting. Also ensure that | the siteURL is set correctly. |In v7.9.4, backported a fix related Oauth 2. Query times depend on if you have rows to delete or not.
With no rows to delete:
- MySQL v5.7.12: 9ms
- PostgreSQL v10: 21ms
4 rows:
- MySQL v5.7.12: 17.2ms
- PostgreSQL v10: 9.9ms
Those times are based off the following table sizes:
- Preferences: 2 million records
oauthaccessdataand sessions: 10 records
You can assess the number of impacted rows by running the following:
PostgreSQL:
SELECT count(o.*)FROM oauthaccessdata o WHERE NOT EXISTS ( SELECT p.* FROM preferences p WHERE o.clientid = p.name AND o.userid = p. userid AND p.category = 'oauth_app' );MySQL:
SELECT COUNT(o.`Token`)FROM OAuthAccessData oLEFT JOIN Preferences p ON o. clientid = p.name AND o.userid = p.userid AND p.category = 'oauth_app'INNER JOIN Sessions s ON o.token = s .tokenWHERE p.name IS NULL;Locks on the oauthaccessdata and sessions table will only be acquired if there are rows to delete.
ServiceSettings.AllowCorsFrom | configuration setting. Also ensure that | the siteURL is set correctly. |ServiceSettings.AllowCorsFrom | configuration setting. Also ensure that | the siteURL is set correctly. |PostPriority setting. |PostPriority setting. |In v7.8.5, backported a fix related Oauth 2. Query times depend on if you have rows to delete or not.
With no rows to delete:
- MySQL v5.7.12: 9ms
- PostgreSQL v10: 21ms
4 rows:
- MySQL v5.7.12: 17.2ms
- PostgreSQL v10: 9.9ms
Those times are based off the following table sizes:
- Preferences: 2 million records
oauthaccessdataand sessions: 10 records
You can assess the number of impacted rows by running the following:
PostgreSQL:
SELECT count(o.*) FROM oauthaccessdata o WHERE NOT EXISTS ( SELECT p.* FROM preferences p WHERE o.clientid = p.name AND o.userid = p. userid AND p.category = 'oauth_app' );MySQL:
SELECT COUNT(o.`Token`)FROM OAuthAccessData oLEFT JOIN Preferences p ON o. clientid = p.name AND o.userid = p.userid AND p.category = 'oauth_app'INNER JOIN Sessions s ON o.token = s .tokenWHERE p.name IS NULL;Locks on the oauthaccessdata and sessions table will only be acquired if there are rows to delete.
ServiceSettings.AllowCorsFrom | configuration setting. Also ensure that | the siteURL is set correctly. |ServiceSettings.AllowCorsFrom | configuration setting. Also ensure that | the siteURL is set correctly. |In v7.8.11, improved performance on data retention DeleteOrphanedRows queries.
New migration for a new table:
MySQL:
CREATE TABLEIF NOT EXISTS RetentionIdsForDeletion(Id VARCHAR(26) NOT NULL, TableName VARCHAR(64), Ids json, PRIMARY KEY (Id ), KEY idx_retentionidsfordeletion_tablename (TableName)) ENGINE = InnoDB DEFAULT CHARSET = utf8mb4; ``PostgreSQL:
CREATE TABLEIF NOT EXISTS retentionidsfordeletion(id VARCHAR(26) PRIMARY KEY, tablename VARCHAR(64), ids VARCHAR(26) []); CREATE INDEXIF NOT EXISTS idx_retentionidsfordeletion_tablename ON retentionidsfordeletion( tablename); ``Hard deleting a user or a channel will now also clean up associated reactions.
Removed feature flag DataRetentionConcurrencyEnabled. Data retention now runs without concurrency in order to avoid any performance degradation.
Added a new configuration setting DataRetentionSettings.RetentionIdsBatchSize, which allows admins to configure how many batches of IDs will be fetched at a time when deleting orphaned reactions. The default value is 100.
PostPriority | setting. |PostPriority | setting. |false for self-hosted deployments.ServiceSettings.TrustedProxyIPHeader defaults to empty from now on. A previous bug prevented this from happening in certain conditions. | Customers are requested to check for these values in their config and set them to nil if necessary. See more details | here. |ServiceSettings.TrustedProxyIPHeader defaults to empty from now on. A previous bug prevented this from happening in certain conditions. | Customers are requested to check for these values in their config and set them to nil if necessary. See more details | here. |New schema changes were introduced in the form of a new index. The following summarizes the test results measuring how long it took for the database queries to run with these schema changes:
MySQL 7M Posts - ~17s (Instance: db.r5.xlarge)
MySQL 9M Posts - 2min 12s (Instance: db.r5.large)
Postgres 7M Posts - ~9s (Instance: db.r5.xlarge)
For customers wanting a zero downtime upgrade, they are encouraged to apply this index prior to doing the upgrade. This is fully backwards compatible and will not acquire any table lock or affect any existing operations on the table when run manually. Else, the queries will run during the upgrade process and will lock the table in non-MySQL environments. Run the following to apply this index:
For MySQL: CREATE INDEX idx_posts_create_at_id on Posts(CreateAt, Id) LOCK=NONE;
For Postgres: CREATE INDEX CONCURRENTLY IF NOT EXISTS idx_posts_create_at_id on posts(createat, id);
ServiceSettings.TrustedProxyIPHeader defaults to empty from now on. A previous bug prevented this from happening in certain | conditions. Customers are requested to check for these values in their config and set them to nil if necessary. See more details | here. |ServiceSettings.TrustedProxyIPHeader defaults to empty from now on. A previous bug prevented this from happening in certain | conditions. Customers are requested to check for these values in their config and set them to nil if necessary. See more details | here. |call into separate submit, form, refresh and lookup calls. If any users have created their own Apps, they have to be updated to the new system.ServiceSettings.TrustedProxyIPHeader defaults to empty from now on. A previous bug prevented this from happening in certain | conditions. Customers are requested to check for these values in their config and set them to nil if necessary. See more details | here. |ServiceSettings.TrustedProxyIPHeader defaults to empty from now on. A previous bug prevented this from happening in certain | conditions. Customers are requested to check for these values in their config and set them to nil if necessary. See more details | here. |mattermost version CLI command does not interact with the database anymore. Therefore the database version is not going to be | printed. Also, the database migrations are not going to be applied with the version sub command. | A new db migrate sub command is added to enable administrators | to trigger migrations. |mattermost version CLI command does not interact with the database anymore. Therefore the database version is not going to be | printed. Also, the database migrations are not going to be applied with the version sub command. | A new db migrate sub command is added to enable administrators | to trigger migrations. |ServiceSettings.TrustedProxyIPHeader defaults to empty from now on. A previous bug prevented this from happening in certain | conditions. Customers are requested to check for these values in their config and set them to nil if necessary. See more details | here. |ServiceSettings.TrustedProxyIPHeader defaults to empty from now on. A previous bug prevented this from happening in certain | conditions. Customers are requested to check for these values in their config and set them to nil if necessary. See more details | here. |ThreadAutoFollow has been changed to false. This does not affect existing configurations where this value is already set to true.ServiceSettings.TrustedProxyIPHeader defaults to empty from now on. A previous bug prevented this from happening in certain | conditions. Customers are requested to check for these values in their config and set them to nil if necessary. See more details | here. |ServiceSettings.TrustedProxyIPHeader defaults to empty from now on. A previous bug prevented this from happening in certain | conditions. Customers are requested to check for these values in their config and set them to nil if necessary. See more details | here. |ThreadAutoFollow has been changed to false. This does not affect existing configurations where this value is already set to true.While trying to upgrade to a Mattermost version >= 6.0.x, you might encounter the following error: Failed to alter column type. It is likely you have invalid JSON values in the column. Please fix the values manually and run the migration again.
This means that the particular column has some invalid JSON values which need to be fixed manually. A common fix that is known to work is to wipe out all \u0000 characters.
Please follow these steps:
- Check the affected values by:
SELECT COUNT(*) FROM <table> WHERE <column> LIKE '%\u0000%'; - If you get a count more than 0, check those values manually, and confirm they are okay to be removed.
- Remove them by
UPDATE <table> SET <column> = regexp_replace(<column>, '\\u0000', '', 'g') where <column> like '%\u0000%';
Then try to start Mattermost again.
Some breaking changes to plugins are included:
- Support for left-hand side-specific bot icons was dropped.
- Removed a deprecated "Backend" field from the plugin manifest.
- Converted the "Executables" field in the plugin manifest to a map.
platform binary and “--platform” flag have been removed. If you are using the “--platform” flag or are using the platform binary directly to run the Mattermost server application via a systemd file or custom script, you will be required to use only the mattermost binary.ThreadAutoFollow has been added to support Collapsed Reply Threads releasing in beta in Q1 2021. | This setting is enabled by default and may affect server performance. It is recommended to review our documentation on hardware requirements | to ensure your servers are appropriately scaled for the size of your user base. |ThreadAutoFollow has been added to support Collapsed Reply Threads releasing in beta in Q1 2021. | This setting is enabled by default and may affect server performance. It is recommended to review our documentation on hardware requirements | to ensure your servers are appropriately scaled for the size of your user base. |Now when the service crashes, it will generate a coredump instead of just dumping the stack trace to the console. This allows us to preserve the full information of the crash to help with debugging it.
For more information about coredumps, please see: https://man7.org/linux/man-pages/man5/core.5.html.
http://. Organizations using non-secure Mattermost Servers http:// will need to update to Mattermost Server versions 5.16.0+, 5.15.1, 5.14.4 or 5.9.5 (ESR) to continue receiving desktop notifications when using Mattermost Desktop v4.3.0 or later.GoogleSettings.Scope config.json setting is set to profile email and | UserAPIEndpoint setting should be set to https://people.googleapis.com/v1/people/me?personFields=names,emailAddresses,nicknames,metadata per | updated documentation. |GoogleSettings.Scope config.json setting is set to profile email and | UserAPIEndpoint setting should be set to https://people.googleapis.com/v1/people/me?personFields=names,emailAddresses,nicknames,metadata per | updated documentation. |SupportedTimezonesPath setting in config.json and changes to timezones in the UI based on the timezones.json file was removed. This was made to support | storing configurations in the database. |SupportedTimezonesPath setting in config.json and changes to timezones in the UI based on the timezones.json file was removed. This was made to support | storing configurations in the database. |DisableLegacyMfa setting in config.json is set to true and | multi-factor authentication is enabled, ensure your users have upgraded to mobile app | version 1.17 or later. Otherwise, users who have MFA enabled may not be able to log in successfully. | | If the setting is not defined in the config.json file, the DisableLegacyMfa setting is set to false by default to ensure no breaking changes. | | We recommend setting DisableLegacyMfa to true for additional security hardening. |DisableLegacyMfa setting in config.json is set to true and | multi-factor authentication is enabled, ensure your users have upgraded to mobile app | version 1.17 or later. Otherwise, users who have MFA enabled may not be able to log in successfully. | | If the setting is not defined in the config.json file, the DisableLegacyMfa setting is set to false by default to ensure no breaking changes. | | We recommend setting DisableLegacyMfa to true for additional security hardening. |AllowUntrustedInternalConnections setting. | See documentation for more details if you have trouble loading images. |AllowUntrustedInternalConnections setting. | See documentation for more details if you have trouble loading images. |This release includes support for post messages longer than the default of 4000 characters, but may require a manual database migration. This migration is entirely optional, and need only be done if you want to enable post messages up to 16383 characters. For many installations, no migration will be required, or the old limit remains sufficient.
To check your current post limit after upgrading to 5.0.0, look for a log message on startup:
[2018/03/27 09:08:00 EDT] [INFO] Post.Message supports at most 16383 characters (65535 bytes)
As of 5.0.0, the maximum post message size is 16383 (multi-byte) characters. If your logs show a number less than this limit and you want to enable longer post messages, you will need to manually migrate your database as described below. This migration can be slow for larger Posts tables, so it's best to schedule this upgrade during off-peak hours.
To migrate a MySQL database, connect to your database and run the following:
ALTER TABLE Posts MODIFY COLUMN Message TEXT;
To migrate a PostgreSQL database, connect to your database and run the following:
ALTER TABLE Posts ALTER COLUMN Message TYPE VARCHAR(65535);
Restart your Mattermost instances.
RunJobs in the config.json and allow the permissions migration to complete before using Team | Override Schemes. |RunJobs in the config.json and allow the permissions migration to complete before using Team | Override Schemes. |config.json setting PostEditTimeLimit has been updated to accommodate the migration to a roles based permission system. When post editing is permitted, set "PostEditTimeLimit": -1 to allow editing anytime, or set "PostEditTimeLimit" to a positive integer to restrict editing time in seconds. If post editing is disabled, this setting does not apply.- If using Let's Encrypt without a proxy server, the server will fail to start with an error message unless the Forward80To443 |
config.jsonsetting is set totrue.
If forwarding port 80 to 443, the server will fail to start with an error message unless the ListenAddress | config.json setting is set to listen on port 443. |
- If using Let's Encrypt without a proxy server, the server will fail to start with an error message unless the Forward80To443 |
config.jsonsetting is set totrue.
If forwarding port 80 to 443, the server will fail to start with an error message unless the ListenAddress | config.json setting is set to listen on port 443. |
config.json setting set to true to complete the Let's Encrypt certification. |config.json setting set to true to complete the Let's Encrypt certification. |application/json content-type to retain previous behavior./data/<date-of-upload-as-YYYYMMDD>/teams/... of your file storage system.You need to verify settings in the System Console due to a security-related change.
- Go to the the GENERAL section of the System Console
- Click Logging
- Make sure that the File Log Directory field is either empty or has a directory path only. It must not have a filename as part of the path.
rtcd servicertcd service to discover their instance public IP. Only needed if configuring STUN/TURN servers. This requirement does not apply when manually setting an IP or hostname through the ICE Host Override config option.rtcd service to discover their instance public IP. Only needed if configuring STUN/TURN servers. This requirement does not apply when manually setting an IP or hostname through the ICE Host Override config option.})
})
})
Icon badge (dot)
}){kind=icon}
Icon badge (number)
}){kind=icon}
You won't be notified when someone types your nickname unless you add your nickname to the list of Keywords that Trigger Notifications as a notification preference.
From Mattermost v10.8, nicknames display in threaded discussions when available.
You won't be notified when someone types your nickname unless you add your nickname to the list of Keywords that Trigger Notifications as a notification preference.
From Mattermost v10.8, nicknames display in threaded discussions when available.
If your system admin has enabled multi-factor authentication (MFA), you can require a passcode in addition to your password to log-in to your Mattermost account.
You'll need to download a MFA passcode generation app, such as Google Authenticator or a similar app, and then set-up MFA in your Mattermost account.
Download a passcode generation app
- Download Google Authenticator for an Apple device from iTunes
- Download Google Authenticator for an Android device from Google Play
Enable MFA in Mattermost
- Open Mattermost in a web browser or the desktop app.
- In Mattermost, from your profile picture, select Profile > Security.
- Under Multi-factor Authentication, select Edit.
})
- Select Add MFA to Account.
})
- Scan the QR code or enter the Secret provided by Mattermost into the authenticator app.
- In Mattermost, enter the MFA Code generated by the authenticator app.
- Select Save.
If your system admin has enabled multi-factor authentication (MFA), you can require a passcode in addition to your password to log-in to your Mattermost account.
You'll need to download a MFA passcode generation app, such as Google Authenticator or a similar app, and then set-up MFA in your Mattermost account.
Download a passcode generation app
- Download Google Authenticator for an Apple device from iTunes
- Download Google Authenticator for an Android device from Google Play
Enable MFA in Mattermost
- Open Mattermost in a web browser or the desktop app.
- In Mattermost, from your profile picture, select Profile > Security.
- Under Multi-factor Authentication, select Edit.
- Select Add MFA to Account.
- Scan the QR code or enter the Secret provided by Mattermost into the authenticator app.
- In Mattermost, enter the MFA Code generated by the authenticator app.
- Select Save.
This option allows you to switch your login method between using email/username and password and single sign-on credentials.
You can configure this setting using Mattermost in a web browser or using the desktop app.
While you can choose to log in with either set of credentials, you can only enable one login method at a time. For example, if AD/LDAP single sign-on is enabled, you can select Switch to using AD/LDAP, and enter your AD/LDAP credentials to switch login over to AD/LDAP. You'll need to enter the password for your email account to verify your existing credentials. Following the change, you'll receive an email to confirm the action.
This option allows you to switch your login method between using email/username and password and single sign-on credentials.
You can configure this setting using Mattermost in a web browser or using the desktop app.
While you can choose to log in with either set of credentials, you can only enable one login method at a time. For example, if AD/LDAP single sign-on is enabled, you can select Switch to using AD/LDAP, and enter your AD/LDAP credentials to switch login over to AD/LDAP. You'll need to enter the password for your email account to verify your existing credentials. Following the change, you'll receive an email to confirm the action.
textprops.mm_blocks is not set)@<username>, @channel, and @here for notifications.@<username>, @channel, and @here for notifications.channelusernameicon_urlicon_emojiicon_url with an emoji. Use the emoji name (e.g., :tada:). The Enable integrations to override profile picture icons setting must be enabled.icon_url with an emoji. Use the emoji name (e.g., :tada:). The Enable integrations to override profile picture icons setting must be enabled.type- Pre-built plugins
- Built-in slash commands @@ -37,7 +37,7 @@ Mattermost provides a variety of methods to integrate with your favorite tools,
- Webhooks
- Custom slash commands @@ -48,7 +48,7 @@ Mattermost provides a variety of methods to integrate with your favorite tools,
- REST API
- Custom plugins diff --git a/docs/main/integrations-guide/outgoing-webhooks.mdx b/docs/main/integrations-guide/outgoing-webhooks.mdx index 63a6d6fbff8..82fca9817e1 100644 --- a/docs/main/integrations-guide/outgoing-webhooks.mdx +++ b/docs/main/integrations-guide/outgoing-webhooks.mdx @@ -168,7 +168,7 @@ The JSON response can contain the following parameters:
textattachments or props.mm_blocks is set) Markdown-formatted message.attachments or props.mm_blocks is set) Markdown-formatted message.response_typeusernameicon_urlattachmentsOpen Source Add-ons available under Apache v2 and other licenses.
Open Source Add-ons available under Apache v2 and other licenses.
Mattermost Terms of Use
Groups in the database are retained but cannot be used. Memberships are frozen in state for group synced teams/channels.
Mentions for AD/LDAP groups are not shown in the autocomplete menu.
Group mentions are no longer highlighted in text and do not trigger new notifications.