Feature ideas

To extend support for additional AWS resource types in the Port-hosted AWS integration, for DynamoDB Tables, Secrets Manager Secrets, Backup Vaults, Route53 Hosted Zones, VPCs, and Subnets. These resources are currently only available via the self-hosted AWS exporter. Adding support for them in AWS port hosted would be beneficial.

A protected app pointing to portal.azure.com using Microsoft Entra authentication is not currently supported in the iframe widget. Entra requires the client_secret param be passed, but this is not configurable in the iframe. Request is for support to be added for a secure way to achieve this auth flow without having to pass client_secret param.

When looking into the raw data explorer, we are currently unable to know if the data is coming from a resync or from a live event. knowing this will allow us to get to the live events quicker using a filter or filter out live events as needed.

The Actions & Automations tab currently only shows "Successful executions" for self-service actions across all breakdowns (by org, user, role, team). Both total executions and failed executions are missing. The automations section already exposes both Succeeded and Failed columns. We need the following columns added to the actions tables: Total action executions Failed action executions Why: Admins can only see successful action executions but have no visibility into failures or total volume from the same view, creating a blind spot for teams tracking action adoption and reliability

Currently, when a workflow is triggered, the execute button remains enabled. If the workflow takes time to start, users can click the button multiple times, unintentionally triggering duplicate executions. The execute button should be disabled (greyed out) immediately after the first click and remain disabled until the workflow reaches a terminal state (SUCCESS, FAILURE, or DECLINED), preventing accidental multiple executions. Users may unknowingly trigger the same workflow several times in quick succession, leading to duplicate runs and unexpected results.

When we use port CLI, the only way to select a partial list of skills to load to a tool (Cursor, Claude Code, etc). We want to have the ability to add a new skill to a tool without the need to reselect the entire list of skills that were previuosly selected. This should be in a new skills add command in port cli. We would also want to add a skills select command that will only allow us to select the list which will be sent to the tool.

We want to add support for installing the skills from port CLI in VSCode It supports the same hooks as Cursor which you already support so I think this should not be a big effort.

We want to connect to an existing MCP server that supports "Client credentials" . It is hosted in AWS agentcore and we need port to support "Client credentials" to connect to the MCP server.

Today by default when installing an integration we see 3 properties: title, created at, updated at. This requires the end user to spend time for every single integration to show/view the required properties. Integrations should come with a default best practice view to reduce this manual time

Add support for ingesting billing and cost usage data, including consumption, credits, usage-based charges, and gross/net cost by user, org, account, and model. This would help customers monitor spend, understand consumption patterns, and measure cost efficiency.