Mattermost system requirements
The default recommendation for secure deployment is to host Mattermost within your own private network, with VPN clients on mobile, so everything works under your existing security policies and authentication protocols, which may already include multi-factor authentication. This feature’s config.json setting is "IdAttribute": "" with string input.Īvailable in Enterprise Edition E10 and higherĬonfigure security settings for multi-factor authentication. If a user’s ID Attribute changes and the user attempts to login the Mattermost server will attempt to create a new Mattermost user account based on the new ID Attribute and fail since new Mattermost users accounts can’t be created with duplicate email addresses or Mattermost usernames (as defined in the Username Attribute).
This attribute should be an AD/LDAP attribute with a value that does not change, such as username or uid. This is the attribute that will be used to create unique Mattermost accounts. If your team typically uses DOMAIN\username to sign in to other services with AD/LDAP, you may enter a field name that maps to DOMAIN\username to maintain consistency between sites. This attribute can be the same as the Username Attribute field above, which is what is used to identify users in the Mattermost interface, or it can be a different value, for example a User ID number. This value is used to sign in to Mattermost in the AD/LDAP Username field on the sign in page. The attribute in the AD/LDAP server that will be used as a unique identifier in Mattermost. This feature’s config.json setting is "MaxUsersPerTeam": 50 with whole number input.
#MATTERMOST SYSTEM REQUIREMENTS FREE#
In terms of technical performance, with appropriate hardware, Mattermost can easily scale to hundreds and even thousands of users, and provided the administrator believes the appropriate etiquette is in place, they should feel free to increase the default value. At this point organizations are more often “multiple teams of people” and investments in explicitly defining etiquette, such as channel organization or turning on policy features in Enterprise Edition, are often used to scale the high levels of productivity found in a team of people using Mattermost to multiple teams of people. The default maximum of 50 people, is at the extreme high end of a single team of people. In the physical world, a team of people could typically be seated around a single table to have a meal and discuss their project. A team of people is considered a small organization where people work closely together towards a specific shared goal and share the same etiquette.
The Max Users Per Team refers to the size of the “team site” which is workspace a “team of people” inhabits. Maximum number of users per team, excluding inactive users.
You can modify the configuration file using the System Console, or by using a text editor to modify it directly. Mattermost configuration settings are maintained in the configuration file config.json, located in the mattermost/config directory.