Development of this feature started.
This will most likely finish in Q4 instead of Q3.AdminSven Hoffmann (Product Owner, COYO) shared this idea ·
now is understand you use case. If I understood correctly you would like to have a page that every user (also newly created ones) follow automatically. But it is up to them to unsubscribe from that page.
You are right - this is something that is not possible right now. I renamed this suggestion to make it clearer what this is about. Hope that's alright for you.
Hey Julia, this should actually be possible. The creator of a page can remove the must-follow setting and then all users can decide to unsubscribe from that page.
There was another discussion about it going on here http://community.coyoapp.com/forums/306010/suggestions/32918209 which might be interesting for you.
Ok, I see your point. The current email notifications work for users that have COYO opened most of the times anyways. They don’t work well for users who visit COYO if something happened that need their attention.
We will have a closer look into this. So, if I git it right it would be sufficient to display more information about the notifications and new posts (e.g. what kind of notifications, excerpt of the post, source of the post etc.)
What about the private messages? Would be it be sufficient to just have the number of new private messages? From my point of view a private message is always something that needs my attention regardless of the actual content.
Hey Julia, I can't provide you with a date, yet. But we are aware that this is very important for you and we have this issue on our list.
Hey Susanne, from a technical point of view it would be possible to do that. But there were two reasons why we didn't:
1. Make the users more curious to actually open COYO and see what's new
2. Some regulations of work councils of some of our customers
But let's see - if people like this idea and vote for it there might me something we can do :)
Since we are replacing the current rich text editor we need to rethink this idea as well.
Internal link previews in timeline posts are going to be part of the major release 11.x.
There are several studies showing that a mechanism forcing users to change their password on a regular basis does not add any security to a platform.
Therefore it's something we are probably not going to implement.
We are thinking about this feature for quite a long time already. This might be problematic with working councils and data protection, though.
Ok, good idea. I would also be very interested whether other customers have the same problems as well.
We are always trying to optimize the frontend performance of COYO and we did so along the last releases. It has become a very complex application and especially the timeline already has a lot of UI components that might slow down certain browsers.
So, we are always interested in feedback where we can improve speed and performance.
Hey Frank, I am very sorry to hear that. We are already continuously improving the performance of the platform but we will take an extra look into this.
Therefore, can you tell me what browser and which operating system you are using?
Hey Florian, can you give me few more insights? What browser are you using? What device are you using? What exactly hangs and lags? Can you reproduce the issue?
Hey Enrico, generally it is possible to invite groups to workspace. But I guess you mean inviting groups to workspaces and hold them in sync? So, that members being added to a group automatically receive an invitation and users being removed from a group are also being removed from the workspace?
right now we don't have the intend to implement this. We discussed having dynamic workspace invitations in the past many times. In the end we always came to the conclusion that this does not work well with our given concept how workspaces work and that you want to have full transparency on who gets invited and who doesn't.
It is not obvious for the user when invitations are send just because someone changed a group or the group got changed via LDAP sync. The problem will be that admins might loose the overview of who gets invitation and who doesn't. It's easier to have a straight concept that declares groups in the context of workspaces as a help to invite many users at once. The creator and admin of a workspace should be in charge of inviting or removing members.
If one needs dynamic assignments via groups pages might be the way to go instead.
Configuring notifications on a per page / workspace basis could get quite complex, in my opinion. Would it be an option to generally set what kind of notifications you would like to receive? E.g. disable notifications about new members in general?
What exactly is the use case behind this? Would it help to make this smarter? For example, open the tab that had the most recent change? Or the tab I opened the last time?
From my point of view it makes sense as soon as there is more than one share of the same content. If you put the option to the share itself on the timeline - which share is going to be deleted? Additionally, you can't delete shares of other users.
I have to admit that the function is quite hidden but I can't think of an easy way to change this.
Do you mean when you click on the link that someone posted or if someone shared the workspace? I first thought this would be the case when you are on the workspace overview or when clicking the notification - but this is handled correctly.
Agreed. This should definitely be a feature of any forum.
As Sven already stated we started with creating concept and visuals. However, development of this improvement has not started yet but is still planned.
Yes, it is :)
Ah, I see - now I understand. The COYO application name is still set in the sender's email address when using the cloud.
Yeah, you are right. There is no way to change that, right now. An admin setting to set the email address would solve this, right?
Hey Stefan, email notifications can be completely translated in admin backend. Where exactly do want to have the word "COYO" to be exchanged to something different?
If you can go without that actual feature for a while, it should be no problem to migrate, from my point of view.
I know that some customers are actually doing that. They migrate to COYO4 and apply a very restricted role to their former external users (e.g. so that they can only see workspaces). After we implemented the feature itself, it will be possible to "demote" common users to externals.
I am very sorry but I have to announce that we need to postpone that feature again. Development has already started and is ongoing but the feature turned out to be way more complex and difficult than we thought.
It is now scheduled for Q3.
Although development already started we needed to postpone this feature to Q2 as well :(
Correct, It's still planned for Q1 2018.
If the channel owner (and only admin) leaves a channel, all members of the chat become admin. I guess the only problem right now would be that this is not happening when a user gets deleted / deactivated, right?
Can you explain a little bit about the use case behind this idea?