Description of norms on Mattermost Community server

What is the Mattermost pre-release server?

The Mattermost pre-release server runs the latest builds of Mattermost's software, including all open source code for Mattermost Team Edition as well as commercial code for Mattermost Enterprise Edition.

It has three objectives:

  • Provide a workplace for Mattermost Staff

  • Test pre-released builds of our core products

  • Engage with our communities including contributors and partners

The Mattermost pre-release server is NOT A PRODUCTION SERVER. It is a live view of work-in-progress and will contain bugs and have occasional downtime.

You can reach the server at:

The server is also available via the URL which receives the same regular pushes of partially tested code as and which offers daily builds.

The server has two teams:

Contributors Team


Available to anyone who'd like to join the server using either an email and password account (you can sign-up for a free account online) or a Mattermost staff account, which is set up via OneLogin and requires MFA either through OneLogin or Google Authenticator

Staff Team


A confidential space for Mattermost staff requiring a Mattermost OneLogin account and MFA.

Staff Usernames on the Mattermost Server

All Mattermost staff hired after Jan 1, 2020 should have a username in the form of @[FIRST_NAME]_[LAST_NAME] for example "Alice Evans" should be alice.evans

If there are duplicate first name and last names, the new person added should add a middle initial in the form of @[FIRST_NAME].[MIDDLE_INITIAL].[LAST_NAME] for example, "Alice Janice Evans" who joined after the first Alice Evans would be @alice.j.evans.

There are some user accounts that for legacy issues cannot use this format, for all other Mattermost staff--even those who joined before Jan 1 2020--should use the format that creates the most clarity.

Not mentioning staff while referring to them

By default, people's user names and first names trigger mention notifications in Mattermost. This can be distracting if people have the same first names, for example there are multiple people named "Chris" at Mattermost. If you want to mention someone without triggering a notification consider using their three letter initials, for example, "Alice Emily Evans" would be AEE.

As an alternative to saying @alice.evans using AEE lets you refer to the person in passing without pushing an alert to them. For staff members that want to be alerted to even passing mentions of their name, they can opt into that model by creating a keyword notification on their three letter initials.

Key Channels for Staff

The following table lists popular channels for Staff:



Explanation and Link

ANNOUNCE Asynchronous Announcements


Public channel in STAFF team for making staff-wide announcements

ANNOUNCE Synchronous Announcements

Customer Obsession Meeting

Public channel in STAFF team for weekly all-staff meeting (see link in header for more info on "COM", past recordings and materials, etc.

ANNOUNCE New Staff Announcements


Public channel in STAFF team for announcing and welcoming new staff members

Channel Naming Conventions

Any Mattermost staff member can create, rename and archive channels on the pre-release server. When channels don't contain sensitive information they should default to Public channel in CONTRIBUTORS team and welcome participation by contributors.

For example, the Loc: Seattle channel can be joined any contributor, partner or staff member to socialize with our community.

We trust our staff to use names that are fast, obvious, forgiving, and also to help our colleagues with constructive suggestions when names could be improved through iteration.

The following conventions are in place for channels with common purposes:


Naming Convention


BUILD Translation Discussion

i18n: [LANGUAGE]

Public channel in CONTRIBUTORS team for collaborating on translations in different languages

BUILD Build EE with community


Public channel in CONTRIBUTORS team for openly discussing Enterprise Edition features with the public

SOCIALIZE Discuss geographic locations


Public channel in CONTRIBUTORS team for socializing with contributors including staff, partners and technical contributors in specific geographies.

Use cases: Organize social and professional meet-ups

SUPPORT Support PS customers

PS: [Customer Name]

Private channel in CONTRIBUTORS team Channel for Premier Support customers engaging with senior Support Engineer


Work with partners

Partner: [Partner Name]

Private channel in CONTRIBUTORS team for discussions with close partners and Mattermost staff

OPERATE Plan, review and iterate on company operations with MLT


Private channel in STAFF team for topic-specific channels for members of Mattermost Leadership Team to work on Mattermost cadence, E.g. MLT Daily, MLT R&D, etc.

OPERATE Plan, review and iterate on company operations with MLX


Private channel in STAFF team for topic-specific channels for members of Mattermost Leadership Extended Team. E.g. MLX Recruiting, MLT HR, etc.