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.

From the beginning, Cohero has acknowledged 'Groups' and 'Members'. Groups were typically leveraged to gather different people together to represent a . 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 : Teams and Departments.

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:

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:

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 , 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:

We've made a set of strong enhancements to our Share Menu, enabling users with manage permissions to:

We are introducing the Activity Log, designed to support auditability and regulatory compliance.

The Activity Log provides a complete, time-stamped record of who performed which action, when it occurred, and on which asset version, ensuring full traceability across the asset lifecycle.

It captures:

This feature strengthens governance, accountability, and change control by maintaining a transparent and auditable activity history.

We have enhanced the approval response modal, to enable approvers to add a(n) (optional) comment along with their response. This gives approvers a way to provide some more context behind the final decision. Comments provided in the context of an approval, are immediately reflected on the comments panel – intuitively recognizable in that context, and reflecting the approval step as well as the final response provided. The comments are also parsed in the notification email to the asset manager.