Feature Requests

Currently, the API Key Id is a randomly generated UUID, which is not very human-readable. When used in external systems, one could consider deriving a prefix such as some-api-key from the name "Some API key" by lowercasing it and replacing all chars not matching [a-z] by - or similar. Still adding a random suffix to ensure uniqueness is a good idea probably! This would result in client_id values which can be easily correlated with meshStack API Keys, even in external systems. Also configuration errors (using the wrong client_id ) are easier to spot. Also logging is improved, see https://feedback.meshcloud.io/feature-requests/p/display-api-user-and-api-key-information-in-logs

As a user I want to see an overview of all my workspaces when I log in. I also want to see this overview when clicking on the icon in the top left corner. Background info: We conducted user tests and noticed all users expected an overview like that and were confused on how to change to another workspace. Some didn't even realize they had access to more than one workspace and did not understand what a workspace was.

Observation: When creating / saving a building block revision, changes are no more visible traceable. Expectation / Feature Request: If a building block draft is no more required, it shall be discardable.

As a platform engineer, I would have preferred a more concise description — ideally by embedding the Shared Responsibility README directly here, or at least by providing a clear reference to it. Including that context upfront helps ensure everyone understands the boundaries and responsibilities without ambiguity.

When a meshStack administrator rejects a tenant deletion request, the rejection reason is not optimally communicated to the requester. Users must navigate to Compliance > Events and manually search for the corresponding log trail to find the reason. A notification within the meshStack UI would be more appropriate, as this would deliver the rejection reason directly to the requester, eliminating the need for manual searching.

The notification warning is not very helpful as I would need to search all projects in order to find the "two" the message is referring to – there should either be a hint how I can filter or look for those projects(as a user, not an admin). Or the names / links to the projects should be listed in the notification, too. Maybe also a new tab with those projects is a good idea, similar to the expired-access tab.

We are running private cloud platforms managed with meshStack. A key requirement for us is to be able to prominently announce scheduled maintenance events and service disruptions to our users via meshPanel. We've found that the new Communication Center, while useful, doesn't meet the needs for urgent announcements as well as the deprecated "Platform Notifications" (phased out in 2025) did. Previously, Platform Notifications were shown as a highly visible banner on affected workspaces. This was very effective. The new communications are presented on the workspace overview dashboard, but they are not as prominent and can be missed by users. We would like to request a way to display critical announcements (like maintenance or disruptions) as a prominent banner, similar to the functionality we had before.

As an application team I want to see all objects (projects, tenants, building blocks) in my workspace so I can easily find what I am looking for without needing to understand the hierarchy of meshStack

The use of the US date format in the English meshStack UI is non-standard across most European regions. It would be beneficial to allow users to specify their preferred date format.

To make the marketplace better looking we should show all marketplace services in a grid view.