Feature ideas

Sometimes there is a need to create multiple Port "Workspaces", for example, for staging and prod versions of Port. We would like to add the ability to create several workspaces to an organization and to be able to easily switch between them via Port's UI.

Enhance user management capabilities by introducing granular visibility and administrative control over Personal Access Tokens (PATs). This includes the ability to view, audit, and manage PATs created by users, as part of broader advanced access governance. Key Capabilities: List which users have active PATs Display PAT metadata: creation date, expiration Enable token revocation through UI or API Support auditability and security compliance This feature would strengthen Port’s administrative tooling by addressing a key gap in access management and improving overall platform security posture.

Currently, the SCIM integration operates in the background to ensure secure access to Port. However, it is not fully integrated into the application—provisioning does not add users to Port, and deprovisioning does not remove them. Ideally, the SCIM integration should be fully implemented and seamlessly connected with Port.

Allow customers to configure and manage SSO directly in Port UI without requiring support or customer success assistance. Proposed Solution: Introduce a self-service SSO feature that enables Port administrators to configure and manage SSO directly in Port UI without requiring support or customer success assistance. This feature should include native support for major providers like AzureAD and Okta, ability to test it before enforcing, and ability to apply additional provisioning like SCIM.

In scenarios where multiple (and growing) numbers of Kubernetes clusters exist in a customer environment, using one exporter per cluster won't be feasible; therefore, it would be important for the K8s exporter to be able to extend to multiple clusters.

Managing data (sending and viewing) in separated blocks (pagination) in audit logs

Add an option in the widgets to allow users to choose how monthly time intervals are calculated either from the start of the calendar month (1st of every month to end of month) or using a rolling last 30-day period. This will help avoid confusion in date labelling and improve consistency in monthly data visualization.

Allow users to build their own interface components as widgets, with Port's catalog context at hand.

We prefer to deploy through certified marketplace listings for easier deployment and compliance.

It seems that admins can update the "status" of an automation run, but this has little impact on a run that is currently in-progress. For example, where an automation kicks off a Github Actions workflow backend. We should be able to cancel the run via the Port UI. In particular this would be useful to "bulk-cancel" a large number of runs - e.g. when an automation is misconfigured, and has initiated a significant number of runs.