Feature ideas

We would like to request an enhancement to the Usage Dashboard by adding a Failed executions column to the Action tables. Currently, the tables only include a Successful executions column, which provides an incomplete view of action outcomes. Including failed executions alongside successful ones would give users a more comprehensive understanding, and make it easier to identify failure patterns and overall reliability at a glance.

Summary: Port's aggregation properties support $team (entity ownership) as a path segment, but only when it is the first hop in a pathFilter. When $team appears as a mid-path hop, the traversal silently returns 0 — even when the underlying data is correctly modeled. Example path that doesn't work: EntityA → relation_to_EntityB → $team(_team) → domain Why it should work: Every Port entity already carries a .team[] ownership array. The graph connection exists natively — Port just doesn't traverse it mid-path in the aggregation engine. No additional relation is needed; the data is already there. Current workarounds (all have trade-offs): Add a redundant direct relation (e.g. EntityB → domain) — requires ongoing maintenance Add an explicit _team relation — forces internal Port concepts into the data model Expected behavior: $team should be resolvable at any position in a pathFilter path, consistent with how it behaves as a first-hop segment.

With the new AWS Integration, we would like to ingest data from AWS CodeBuild, AWS CodeDeploy and AWS SES.

At the moment, port will sort the orgs in the multi org switcher according to the last org that was logged in to. We want to be able to set a sort to the list and configure the order of the orgs in the multi org switcher.

Currently the audit log only shows when an action's permissions were updated, but it doesn't show what the actual permission changes are. This is crucial for debugging permission issues and tracking changes.

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

Currently, when an admin impersonates a user and initiates a self-service action, the triggered by field reflects the admin rather than the impersonated user. This causes issues when supporting users. It would be beneficial to default this field to the impersonated user or provide a prompt to select the user when starting the action.

Current Behavior: When a Port integration is deleted, its associated secrets stored under Credentials → Secrets are not automatically removed. These stale secrets persist and can cause a "secret already exists" error if a user attempts to recreate the same integration type later. Desired Behavior: When an integration is deleted, Port should either: > Automatically delete all secrets associated with that integration, or > Display a prompt/warning during the deletion flow reminding users to manually clean up the associated secrets to avoid conflicts on re-creation.

Bring your own MCP. Port’s AI today only sees what’s inside Port. By bringing in a customer's MCP Server and their AI Agents, they are already pulling in external context from Confluence, Jira, and other systems. Their AI Agents may have deep context surrounding their business. Customer wants Port to be able to tap into that external intelligence so the AI inside Port can act with full awareness of both Port and non-Port data.

I just need a way to set a custom URL, and set what model I want to use. We're effectively using bedrock, however we want to be able to control credit usage on a per user basis and potentially charge those to their relevant AWS accounts, hence wanting to use a proxy.