110 results found

1. Plugin hooks for access control and logout events

   Add server plugin hooks for access control (permission change) and logout events to enable developers to create custom server plugins to integrate with internal auditing/intrusion detection tools.

   https://developers.mattermost.com/extend/plugins/server/reference/#Hooks

   16 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Mattermost Enterprise Edition  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Implement ~{channel_name} Feature for Private Channels and Direct Messages

   The current ~{channel_name} feature only works for public channels.

   As of now, users are able to obtain the URL of the private through the "View Info" feature.

   Another option is to right click the room name on the channel list and click "Copy Link".

   It will be good to standardize the feature across all types of channels to for a better user experience.

   15 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Mattermost Enterprise Edition  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. New Channel Announcements

   When people create new channels within a team, it would be great to have a popup that shows team members within the channel a screen something like "New Channels created since your last visit, refresh, etc..."

   What we are finding is people are creating new channels within Teams, yet no one knows about them unless they click on the More link within the team.

   14 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  Mattermost Enterprise Edition  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. A format for coloring text

   Hello dear friends

   Given that there is no format for coloring part of the text
   Please vote to add this format to this post.

   Colored text is very necessary to send a message and emphasis

   14 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  Mattermost Enterprise Edition  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Server-wide categories for your sidebar

   The new feature "costume category" gives the option to re-sort your channels and also Direct Messages.
   It would be great if that would work Server-wide and not only Team-wide.
   Exspecially for Direct Messages it would help to be able to sort them. It could work like the "Favorite" which is also server-wide.
   It could also be an option to have it server-wide optional by a setting

   12 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Mattermost Enterprise Edition  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Report duplicate AD/LDAP information rather than setting usernames to random strings every hour

   When the AD/LDAP User Filter is too permissive, multiple user objects with the same Email Attribute may be returned. When this happens, and the Username Attribute is not present on the returned value, Mattermost may reset the username of the existing user with the same email address to a random string. This repeats every 60 minutes (or whatever the Synchronization Interval is set to).

   For example, if two LDAP objects are returned:
   { userclass=contact, email=myusername@example.com }
   { userclass=user, sAMAccountName=myusername, email=myusername@example.com }

   In this case, Mattermost may cause username@example.com's account to have its user id changed to a random 37-digit base-36 number

   When this occurs, tracking the problem down is very difficult. The only information in the logs is that the username for several accounts changes to a new random value every hour.

   To make this simpler, Mattermost's logs should indicate when the AD/LDAP system returns duplicate entries for the ID attribute.

   (Mattermost Support suggested I file this as a Feature Request, although it feels like a bug)

   When the AD/LDAP User Filter is too permissive, multiple user objects with the same Email Attribute may be returned. When this happens, and the Username Attribute is not present on the returned value, Mattermost may reset the username of the existing user with the same email address to a random string. This repeats every 60 minutes (or whatever the Synchronization Interval is set to).

   For example, if two LDAP objects are returned:
   { userclass=contact, email=myusername@example.com }
   { userclass=user, sAMAccountName=myusername, email=myusername@example.com }

   In this case, Mattermost may cause username@example.com's account to have its user id changed to a… more

   11 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Mattermost Enterprise Edition  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Add a feature to create custom command alias within Mattermost client

   We would like a feature to allow leveraging slash command integrations so that users could create custom aliases locally. For instance, one of our integration commands is '/zoom' with additional arguments of 'join' and '<meeting ID>'. We would like to be able to create a custom alias so that a user could always include the arguments along with the slash command without entering 'join' and their 'meeting ID' each time they use the integration.

   11 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Mattermost Enterprise Edition  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Limit direct messages per User

   We would like the users to focus on channels. Although we do not want to disallow direct messaging at all.

   It would be amazing if we could set a direct message limit per day.

   For example: User X is allowed to send 20 direct messages per day, while User Y can send unlimited direct messages.

   With this feature we don't limit the users too much, but we also make sure that important information is held in the channels.

   11 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Mattermost Enterprise Edition  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Chat left/right alignment

   Does mattersmost have a feature to make chat like SMS or MSTeams, where the messages sent by yourself are aligned to the right side of the screen and messages from others are on the left side?

   10 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   under review  ·  0 comments  ·  Mattermost Enterprise Edition  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Ability to customize the chat display/layout

    Add a way to customize the display of the chat in the web interface. Currently a single message takes up two lines of text. If each message could be formatted as desired, the layout could be tailored to each users preference.

    For example (with overly descriptive variable names):
    %SENTTIME%| %SENDER%> %MESSAGE%
    Would result in:
    15:56| Kristian> Hello world!

    To build the current view, you could do:
    %AVATAR% %SENDER% %SENTTIMEAGO%\n%MESSAGE%

    Or something like that.

    As a long time IRC user, I feel that the WebUI for mattermost uses way too much space for a simple chat messages. With customized layout, it would also be possible to also show the exact time of a message, rather than "x ago" which I find extremely unprecise. :-)

    Add a way to customize the display of the chat in the web interface. Currently a single message takes up two lines of text. If each message could be formatted as desired, the layout could be tailored to each users preference.

    For example (with overly descriptive variable names):
    %SENTTIME%| %SENDER%> %MESSAGE%
    Would result in:
    15:56| Kristian> Hello world!

    To build the current view, you could do:
    %AVATAR% %SENDER% %SENTTIMEAGO%\n%MESSAGE%

    Or something like that.

    As a long time IRC user, I feel that the WebUI for mattermost uses way too much space for a simple chat messages. With customized layout, it… more

    10 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Mattermost Enterprise Edition  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. End-to-end encryption of mobile notifications

    If a user is sending highly sensitive information over a Mattermost deployment, having it traverse Apple's and/or Google's servers unencrypted en route to a mobile device may not be acceptable. At the same time, configuring the server to exclude the message body removes a significant amount of potentially-valuable context from the notification.

    The conflict between these concerns could be resolved by having the Mattermost server encrypt mobile notifications with a per-device key prior to submission, and having the mobile app decrypt the notification before presenting it to the user.

    This can be done on iOS with a Notification Service Extension: https://developer.apple.com/library/archive/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/ModifyingNotifications.html
    This can be done on Android with FCM data payloads: https://firebase.google.com/docs/cloud-messaging/android/receive

    If a user is sending highly sensitive information over a Mattermost deployment, having it traverse Apple's and/or Google's servers unencrypted en route to a mobile device may not be acceptable. At the same time, configuring the server to exclude the message body removes a significant amount of potentially-valuable context from the notification.

    The conflict between these concerns could be resolved by having the Mattermost server encrypt mobile notifications with a per-device key prior to submission, and having the mobile app decrypt the notification before presenting it to the user.

    This can be done on iOS with a Notification Service Extension: … more

    10 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Mattermost Enterprise Edition  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Disable join/leave messages globally

    It would be nice to disable the join/leave messages independently from the user specific setting. We use a channel to post anonymous posts via a bot. People can see who joined and see a link to an anoynmous post.

    10 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Mattermost Enterprise Edition  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Support for nosql database

    Considering the benefits of data analytics for such kind of apps, don't you think support for a nosql database would help. Also, if you want to scale it to a million users; will a rdbms solution support that?

    9 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Mattermost Enterprise Edition  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Make log file reading easier

    The timestamp within the log is now Unix Timestamp. This makes it really hard to find the right logs when there is a issue.

    Please implement a option to change to a human readable time. I suggest the UTC timestamp. Dateformat can be fix of should better be looking for the server values.

    Now:
    {"level":"debug","ts":1540975612.3137412,"caller":"web/handlers.go:50","msg":"POST - /api/v4/users/status/ids"}

    Better:
    {"level":"debug","ts":10/31/2018 8:46am,"caller":"web/handlers.go:50","msg":"POST - /api/v4/users/status/ids"}

    Optimal (i am in europe):
    {"level":"debug","ts":31.10.2018 8:46,"caller":"web/handlers.go:50","msg":"POST - /api/v4/users/status/ids"}

    Best regards

    9 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Mattermost Enterprise Edition  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Access Control List for Web Interface & Mobile App

    We are a .org wishing to implement Mattermost.

    We would like only a specific group of "internal" users to be allowed to access the server from outside the firewall. In addition, we would also like a specific group of external clients to be able to access the server through the mobile app.

    I understand one method is to use a VPN. However, an additional app to put on someone's device may be a burden.

    The Novell/Micro Focus Product Webaccess has a feature that allows the admin to specify users via an .xml file.

    A snippet:

    "Controlling WebAccess Usage:

    You can control which users can use WebAccess to access their GroupWise mailboxes. By default, all GroupWise users can use WebAccess.

    You can control access based on the domain or post office where the user’s mailbox is located. You can control access for related users based on groups, and you can control access for individual users.

    Access control is established through the gwac.xml file, located in the same folder with the webacc.cfg file.

    The default gwac.xml file illustrates the following options:

    <!-- To allow access to all EXCEPT a few, use this technique. -->
    <!--
    <gwac access="prevent">
    <domain name="domain1" />
    <postOffice name="po2.domain2" />
    <user name="jdoe.po3.domain3" />
    <distributionList name="helpdesk.po4.domain4" />
    <resource name="confroom.po4.domain4" />
    </gwac>
    -->

    <!-- To prevent access to all EXCEPT a few, use this technique -->
    <!--
    <gwac access="allow">
    <domain name="domain1" />
    <postOffice name="po2.domain2" />
    <user name="jdoe.po3.domain3" />
    <distributionList name="helpdesk.po4.domain4" />
    <resource name="confroom.po4.domain4" />
    </gwac>
    -->
    You can use any ASCII text editor that you prefer to edit the gwac.xml file.

    Open the gwac.xml file in a text editor.

    Typically, you use the gwac.xml file to override the default of allowing all users to use WebAccess.

    Remove the comment marker lines (<!-- and -->) around the section that you want to use.

    (Optional) Under the <gwac access="prevent"> line, create one or more lines to prevent users in one or more domains from using WebAccess, for example:

    <domain name="provo5"/>
    <domain name="provo6"/>
    (Optional) Create one or more lines to prevent users in one or more post offices from using WebAccess, for example:

    <postOffice name="interns.provo1"/>
    <postOffice name="temps.provo1"/>
    Specify the post office in post_office.domain format.

    (Optional) Create one or more lines to prevent users in one or more groups from using WebAccess, for example:

    <distributionList name="webaccessdenied.admin.provo1"/>
    Specify the group in group.post_office.domain format.

    Using one or more groups is the most flexible approach to access control for WebAccess. The group belongs to a specific post office (for example, the one you belong to), but it can include GroupWise users located anywhere in your GroupWise system. By using a group, you can easily modify access control for specific users by modifying the group in the GroupWise Admin console, rather than needed to modify the gwac.xml file whenever access control changes are needed. For more information about groups, see Section 56.0, Creating and Managing Groups.

    (Optional) Create one or more lines to prevent specific users from using WebAccess, for example:

    <user name="sjones.interns.provo1"/>
    <user name="gbock.interns.provo1"/>
    (Conditional) If you want to prevent most users and allow only specified users, use a <gwac access="allow"> line instead of a <gwac access="prevent"> line.

    Save the gwac.xml file."

    Please consider.

    Original Request:
    http://forum.mattermost.org/t/restricting-users-from-accessing-mattermost-outside-firewall/2617

    We are a .org wishing to implement Mattermost.

    We would like only a specific group of "internal" users to be allowed to access the server from outside the firewall. In addition, we would also like a specific group of external clients to be able to access the server through the mobile app.

    I understand one method is to use a VPN. However, an additional app to put on someone's device may be a burden.

    The Novell/Micro Focus Product Webaccess has a feature that allows the admin to specify users via an .xml file.

    A snippet:

    "Controlling WebAccess Usage:

    You can… more

    9 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Mattermost Enterprise Edition  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Increase the maximum nickname length (or a pronoun field)

    In our mattermost, users have been organically adding their pronouns to the end of their nickname, which is great, but when users have particularly long names, it's impossible for them to add more than 22 characters.

    Example: "Joe Smith (he/him)" works fine at 18 characters, but "Alexander Bernard (They/Them)" at 29 characters goes well past the 22 character limit.

    Because of the number of potential duplicate users based on their first name, there just isn't a good way to add pronouns, and it's difficult to explain that the 22 character limit on nicknames isn't able to be extended on our end.

    Please consider extending the maximum length of this field, or adding a separate pronoun field that can be appended to the end of a user's name. It would help in our efforts to be inclusive.

    In our mattermost, users have been organically adding their pronouns to the end of their nickname, which is great, but when users have particularly long names, it's impossible for them to add more than 22 characters.

    Example: "Joe Smith (he/him)" works fine at 18 characters, but "Alexander Bernard (They/Them)" at 29 characters goes well past the 22 character limit.

    Because of the number of potential duplicate users based on their first name, there just isn't a good way to add pronouns, and it's difficult to explain that the 22 character limit on nicknames isn't able to be extended on our… more

    9 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Mattermost Enterprise Edition  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Add GPG signed and encrypted notifications (end to end)

    As administrator I want to restrict notification messages sent from my self-hosted mattermost server to be GPG signed and encrypted.

    That means, if a user hasn't uploaded a GPG public key to his account, notifications sent to him only contain some metadata or nothing at all.
    If a user has uploaded a GPG public key, then the notification message is encrypted for him as receiver, so only he can read it.
    The notification message shall be signed in any case with the private key that I configured in my mattermost server.

    Motivation: transport layer security between the mattermost server and clients is a great thing for transfering confidential information, however, if the receiver happens to be offline/away and notifications are configured to contain the content of the message it results in a leak of this sensitive information because the data lands in plain text on foreign mail servers.

    As administrator I want to restrict notification messages sent from my self-hosted mattermost server to be GPG signed and encrypted.

    That means, if a user hasn't uploaded a GPG public key to his account, notifications sent to him only contain some metadata or nothing at all.
    If a user has uploaded a GPG public key, then the notification message is encrypted for him as receiver, so only he can read it.
    The notification message shall be signed in any case with the private key that I configured in my mattermost server.

    Motivation: transport layer security between the mattermost server and… more

    8 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Mattermost Enterprise Edition  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Migrate users from email to GitLab authentication provider using CLI

    I would like to have an opportunity to migrate users from email to GitLab authentication provider - mmctl user migrate-auth email gitlab users.json
    Currently, it is possible to migrate only to ldap or saml.

    GitHub Issue - https://github.com/mattermost/mattermost/issues/24425

    8 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Mattermost Enterprise Edition  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    under review  ·  Adminmattermost.org (Moderator, Mattermost) responded

    Label and status updated.

19. Purge Inactive Users

    It would be great to be able to purge users who have not logged into the site in a definable window.

    7 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Mattermost Enterprise Edition  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Microsoft Active Directory SSO with reverse proxy REMOTE_USER

    For advanced enterprises with sophisticated authentication requirements, this feature would allow authentication through REMOTE_USER information passed in via HTTP headers

    This feature requires a fundamental change to the Mattermost user model so that users can exist outside of teams.

    Several threads have discussed this feature:
    - https://forum.mattermost.org/t/active-directory-sso-through-a-reverse-proxys-remote-user/295
    - https://forum.mattermost.org/t/client-side-certificate-authentication/1174

    7 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Mattermost Enterprise Edition  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating