Welcome to the Ryver Product Ideas forum! We pride ourselves on constantly improving Ryver based on customer feedback. Here, you can view and vote on the current list of feature ideas, or add your own idea if you don't see it.
For immediate support, go to https://support.ryver.com and click the Chat tab in the lower left. You can also request help from the Send Feedback link in the top drop-down menu in the application nav bar.
It would be nice to be able to move a post from one team or forum to another when editing. This could expand on marking posts as "completed" or "archived", as you can just move them to a "completed" forum. We're planning to use this for a question and answer tool, so having an "answered" forum that we can move the older questions into would be very useful.
You have created the most useful communication tool we have ever tested and kudos for making it free!
We have two major concerns:
- Can’t install it on premise.
- Uploaded files go to Amazon cloud and are accessible by simply sharing the link even to people that are not members or guests to our Ryver organization.
Solving either of these concerns would resolve the other – if we had on-premise installation we could host our files locally, and if the uploaded files were encrypted or hosted in directories that are not publicly accessable from the internet we would not have issue with Ryver not being on-premise.
I would propose two types of solution that would not require on-premise installation:
- A quick and dirty fix in the form of a checkbox that allows the administrator to disable all file uploads for everyone (at least untill the second solution is implemented).
- Some sort of cookie or session authetication that would allow file download from the amazon storage only if the user is currently logged onto our Ryver. This can be further extended to special group file access but I understand that that can take some more time to develop.
You have made communicating and sharing ideas and files so easy that I am sure I would not be able to put forward policies on which files should and shouldn’t be shared in Ryver, so why limit people when we can make it secure and let them communicate freely.
I wish you all the positive energy in the universe and I hope you get the success you deserve!
When using the @name in a chat or post it would be awesome if the name that went into the chat or post was the display name instead of the actual @username. For example if my username is @jmaxwell and my display name is "John 647" (where 647 is a location number) or "John Maxwell" it would be nice to have the display name inline in the chat as everyone may not know who jmaxwell is but they may know who "John 647" is. I hope I am being clear in what I am trying to ask for. This could be categorized in Chat or Post as it is the same for both.
It would be great to see how long a user has been idle/away in mins/hrs Skype for Business (formerly Lync) had this feature. It would also be nice to be able to set the time limit for how long it takes for a user to go idle/away. Currently i think Ryver default is set to 30 mins.
Thanks for considering.
Unless i am missing something, i can currently add only individuals to a team. In a cross-functional or matrix organization, it means that i will be doing a lot of manual additions, one person at a time. Instead, it will be much easier, and much more reflective of the groups-interacting-with-group picture you had delineated in your product announcement, If i can add a team to a new team.
It will save a lot of manual additions, and not only in the first time. If i later make changes to a team, these changes will be automatically reflected in all teams that include them ;-)
the idea here is that during these 1:1 discussions or posts, items may be identified, they may be tasks, or features, or deliverables, etc. It would be super useful to be able to create a new list during a conversation (through a bot tag #list New Features, etc.) and then during the conversation be able to add items to the list, again through some tag or bot. I say "lists" to keep it generic and leave it to the user community to decide what the lists will do. The lists could evolve, ie assign an item in a list to a person, add a due date, add it to a release (for a feature), etc. Endless productive possibilities. Thanks, D
As the number of users on an account increases, so does the number of open forums.
Allowing team ownership of forums would help organize many forums that may only be relevant to certain teams. Cutting down on the number of forums everyone else must sort through.
Customer support service by UserEcho