Feature ideas

Expose an MCP of Port with tools LLMs and AI Agents can use to interact and get information from Port

Currently, time-based configurations require manual updates when daylight saving time (DST) changes. This feature request proposes an enhancement to enable the system to automatically adjust for DST without requiring manual modifications. Implementing this would ensure accurate time calculations, reduce the risk of errors, and eliminate the need for repeated adjustments.

In the URL property type settings if there could be a setting to select to change the behavior of clicking the link, either it opens in a new tab or not, or even in a new window, this would help admins curate an optimal user experience.

On a catalog page, the related column in the UI displays the title, the exported CSV shows the identifier instead. Displaying the title in the CSV export would be more helpful.

I want to be able to insert entities by batch or bulk through webhook/REST api to prevent calling the same endpoint many times. I also want to be able to do the same when deleting entities. Having checkboxes in catalogs to select and do a specific action for selected entities can also help :)

This would work in tandem with the suggestion to have multiple workspaces in port (i.e. orgs could have a stage and prod version of port). Essentially, instead of data exporters only sending data to one instance of port - this would allow us to configure exporters / webhooks to send the data to multiple port organizations. The value is that then data can be mirrored easier between stage and production and testing with the data in lowers is more reliable because you have real data to work with.

Add format values e.g. currency, percentage, rounded, 1dp to a number property in a blueprint for when it is displayed either on the specific entity page or in a table Would stop having to define calc properties to get common number formatting options - simplify blueprints and improve display

It is valid for a user to have an apostrophe in their email address. Email address seems to be the defacto value used as an identifier for the system-managed _user blueprint. Example: j.o'bloggs@ourdomain.com Port does not appear to support such an email address. If we attempt to create such a user via the web app: > j.o' bloggs@redacted.com is not a valid email If we attempt to upsert the entity via the Port APIs, the audit log shows an error: > "identifier" must match pattern "^[A-Za-z0-9@_.+:\\/=-]+$"

It would be great to have an option to do bulk actions(day2 and DELETE) on entities

Currently, the number chart types Count Entities and Aggregate by Property include the unit field, but Display Single Property does not. We would like to have the unit field available for the Display Single Property number chart type as well.