Feature ideas

Some customers would like the option to automatically report Port's information to an external SIEM system for security concern. https://www.ibm.com/topics/siem#:~:text=Security%20information%20and%20event%20management,chance%20to%20disrupt%20business%20operations . First and most important are the changes of Port's audit log

Today, when updating new objects / arrays of entities the new value overrides the old one. With this feature it will be possible to append values to these properties. Example of Tags property with type of array: Current state: "Tags" : ["tag1"] Ingesting a new tag using the API: "tag2" New state: "Tags": ["tag1", "tag2"]

The MyTeams option should appear in the filter value dropdown whenever the selected filter property resolves to a team, regardless of whether that property is: A native owning team property on the directly filtered entity A computed team property on the directly filtered entity An owning team property or relation on a related entity (i.e. filtering Entity A by Entity B's owning team) This can currently be achieved using JSON mode filters, but not in the form view with MyTeams.

Add support for reliably identifying the earliest commit & timestamp that belongs to a pull request across GitHub, GitLab, and Azure DevOps, as this is required to calculate Lead Time for Changes regarding DORA metrics.

Currently, permission changes made through Terraform are not captured in the audit logs The request is to add support for logging permission changes triggered via Terraform in the audit logs

Currently, Port's global search only indexes markdown content that is stored as a markdown-type property on a catalog entity (surfaced under the "Tech Docs" search category). Markdown content entered directly into a Markdown widget on a dashboard (using the "Custom" data source) is not tied to any entity and is therefore not indexed or searchable. This is a limitation for teams building customer-facing or internal knowledge bases directly within Port using dashboard markdown widgets. Users expect that articles and documentation written in markdown widgets would be discoverable through the global search, just like entity-bound markdown content.This is a limitation for teams building customer-facing or internal knowledge bases directly within Port using dashboard markdown widgets. Users expect that articles and documentation written in markdown widgets would be discoverable through the global search, just like entity-bound markdown content.

Request to implement consistent guardrail enforcement when triggering self-service actions via the MCP, so that dataset filters and advanced input logic are respected regardless of the execution surface (UI or API/MCP). Currently, the Port MCP bypasses frontend-only input validations (like dataset filters) when self service actions are triggered, allowing LLMs to select any value, which can violate intended permissions/guardrails.

Port's URL and Labeled URL properties are fundamentally different types, once a URL property is created, it cannot be converted to a Labeled URL in place. The only path to migration requires creating a new property, deploying, migrating data, updating all integrations, and deleting the old property, a process that can take ~2 hours for what should be a trivial display change. Proposed Solution Allow a display-layer transformation (e.g., via JQ expression or a simple label mapping) on existing URL string properties, so that: The underlying data remains a plain URL string (no schema change, no integration updates required). The display layer renders the URL with a human-readable label, equivalent to the current Labeled URL behavior. Why It Matters Eliminates data duplication and integration dependencies caused by property recreation. Reduces a ~2-hour migration to a seconds-long configuration change. Aligns with the spirit of the already-shipped Labeled URL feature.

Request for an API endpoint that can retrieve account-level information. This will allow us to retrieve all orgs associated with our account at once, and to edit account name, which isn't currently possible

Expose branch-level data from the GitLab API so Port can ingest it as service catalog properties. Specific fields needed: Last commit date (the customer currently has last activity date as a workaround, but wants actual last commit on the default branch) Last commit author (the person who authored the commit, not a bot/merge service account)