Changelog
Follow up on the latest improvements and updates.
RSS
Before we started working on taking Cohero's notifications to the next level, we wanted to improve the way users are informed when they're being mentioned in a comment. The original email that was triggered only contained a signal
that
you were mentioned, but it didn't specify what was said
in that comment. We realized that this was vital context to have, merely to understand the nature of the question (let alone: the urgency go respond). So by popular demand, we improved the email notification for 'mentions'. The email now clearly shows:
- In what context, the comment was made (specifying the name of the project, or the asset)
- Who wrote that comment, and when
- What was the full comment, in which you were mentioned
And of course offers a way to view the comment on Cohero. We hope you enjoy these small updates!

True to their transient role, projects come and go. But despite their temporary purpose, projects can end up containing valuable information (attachments, conversations), next to the reference to the assets that were created in their context. So users feel reluctant to remove them. But without removing projects, over time, projects tend to clutter up spaces - which poses a struggle for our customers.
To help users keep their spaces clean - we're introducing
Project Status
. By changing the project status (either on project cards, or by using the 'Project info' menu on project pages, users now have the ability to mark projects as 'closed' or 'open'. By default, closed projects are hidden on Space pages, but can easily be surfaced by changing the Project Status filter. 


All members with 'Manage permissions' are now capable to toggle an item's visibility (switching between 'public' and 'private'). Earlier, this was only something the original creator of an item could do.
new
Group Types
From the beginning, Cohero has acknowledged 'Groups' and 'Members'. Groups were typically leveraged to gather different people together to represent a
team
. However, not all of these groups are meant to be assigned, mentioned, or even to be invited to an approval. For that reason, we've introduced 2 group types
: Teams and Departments. 
Teams
Teams represent groups of people that play an active role in getting work done. They act as a team, and carry joint responsibility to close on anything assigned to them. This means, teams are:
- Available to be assignedto a task
- Available to be invitedto do an approval (unless not identified as 'eligible')
- Available to be mentionedin a comment/reply
- Available in the Share Menu, to grant access & permissions
Departments
Departments represent groups of people that are united by some kind of organizational logic. It does not mean they operate together, or handle work together, but they're acknowledged as similar from an organizational perspective. This means, departments are:
- Not available to be assignedto a task
- Not available to be invitedto do an approval
- Not available to be mentionedin a comment/reply
- but they ARE available in the Share menu, to grant access & permissions
Acknowledging that our clients seek an even more trusted way to authenticate their members, before entering the workspaces - we have established the foundation for Single Sign-on (SSO). Single Sign-on will be offered in addition to the already available authentication (through a time-sensitive, one-time passcode) for the workspaces that are configured to carry SSO.
The time-sensitive one-time passcode (TOTP) will serve as the way to establish trust between the user and his device. Consequently, the (optional) SSO authentication (required only once) will establish trust between the user's device and the organization's workspace.
With this foundation in place, we can now plan to configure client workspaces with SSO authentication, by tying Cohero to their Identity Providers (IdP).
With a new improvement, users who don't have access to specific items (eg: an asset, or a project) can now request access. When they do so, the creator of that item automatically receives a notification, expressing that that particular user has requested access. He can then come in & give access along with the appropriate permissions.

This simple, but foundational improvement closes the loop on permissions management - and helps to ensure that nobody who needs access, is left stranded.
To further equip workspace admins in managing members in their workspace - we've built a way to see in high detail to which items (Spaces, Projects, Assets) a specific user has received explicit access to. Even better, the admin has a way to see if that access was shared with him/her personally, or via a group (team/department) that members is part of.
This overview is a rather helpful instrument in the context of understanding the access levels of a specific user in a short amount of time
In addition, we've also refined the role descriptions, so that the admins have a better understanding of what roles are able to do.
When your work gets intense across multiple spaces, or when you're visiting a workspace as a
guest user
, it was hard (or as guests: nearly impossible) to locate the items that were explicitly shared with you - without relying on email notifications to find your way again. To accommodate for this, we're introducing a new navigation item called "Shared with me". This item dynamically shows all the assets and projects that you have been explicitly invited to. And needless to say, the page offers plenty of filters and sorting options, to make it easy to overlook.

We've added helpful 'Copy links' options in action menus across the asset page, to enable users to copy (deep)links to various items. With those, user can copy a deeplink and share it (eg: via Teams, chat or email), to send somebody directly to:
- A specific asset version
- A specific task
- A specific comment thread

We've made a set of strong enhancements to our Share Menu, enabling users with manage permissions to:
- Granularly grant or revoke permissions for users and teams, even when items are public;
- Invite Guest Users, members with limited permission sets, to collaborate with you on assets;
- Use the simplified interface to quickly recognize who's been granted access, and what kind of permissions (s)he has on a particular item.


Load More
→