Feature ideas

As admin users, we have full visibility on everything that's available in Port. We can already control what users see and interact with, but we cannot easily confirm if the changes we have made are correctly tailored to them. It would be very helpful to be able to preview the changes.

Currently, you can ingest markdown documents into Port by creating markdown properties. Each document will be displayed in Port as a tab on the specific entity page. We would like to add the ability to create a "documentation tree" for each entity, allowing you to create a full wiki inside your developer portal. Similar to the singular markdown documents, the documents in the "documentation tree" will be searchable via the global search .

Currently, using the dynamic permissions feature, self-service actions will still appear in the UI. In case the user is not permitted, the run will be rejected only after sending the self-service action form. As part of this item, we would like to support hiding/displaying self-service actions using the dynamic permissions policies.

Chain multiple inputs, approvals, conditions, and actions via automatic triggers or self-service

Surface client secret rotation events in audit logs, including who initiated the rotation and when it occurred. This enables to trace unexpected rotations, improve visibility,until approval-based rotation is available.

We recently deployed a SonarQube integration using the hosted solution. Due to our custom IaC setup, we use non-standard blueprint names, but the integration continues to install blueprints and pages with default names. I attempted to disable this using the initializePortResources: false option in the configuration, but it had no effect. It would be helpful to have an option to completely disable the creation of default resources.

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

Allow combining lines from different types: Count Entities, Aggregate Property and Property History.

Currently Terraform has only partial page management, with the ability to edit basic pages such as dashboard and blueprint-table; but it has no support yet for specific entity pages.