Your comments

Yes, this issue should have been addressed quite some time ago. We are going through the site and catching up now, and will plan to move forward with much more active monitoring.

Ok, with the changes we just made to our chat server in the latest upgrade, we are now going to be able to process each message and look for any @mentions behind block quotes. We will put code in place to NOT do the notification if that is the case.

Sorry, this has been fixed to the best of our knowledge for several months, and we didn't close this out. Please contact support if you are seeing this issue in version 1.2.0 or higher of the desktop client.

Strange! We'll try to reproduce that one this morning, as our webhooks have all been showing up in the "All Webhooks" list.


Were you using the Ryver desktop client? And if so, do you have the latest 1.2.0 version of the client from ryver.com/downloads? (version under Help > About)

Hmm...so maybe if the Admin could click on a user avatar and see the email in the pop-up profile card?

We'll look into this option of floating the day. We've moved most of our UI views to React, with Chat and Posts being the last two "legacy" views (and the mosts complicated ones). I'll make sure this idea is something that gets considered with the React update!

We had generally figured that people would be chatting/posting in the same language, and that the primary issue is with the app itself, and things like date format. But that widget is certainly an interesting idea!

We will be implementing SAML support over the next couple of months, then taking it live in Q2. With SAML support in there, people will be able to use the SSO management tool of their choice to integrate into AD, etc. I believe this would cover your needs, but please let me know if you need something more specific.


Our next step in terms of doing a more focused SSO integration will likely be related to Google Identity Management for G-Suite applications.

Ok, we've finally gotten around to discussing this a bit more. I don't think we'll be defaulting to Posts (at least not yet), but it does make sense for this to be an Admin option.


Would you want the ability to completely disable the Chat option on a team by team basis? Or is defaulting to POSTS good enough?