Feature ideas

Add an option of mapping integrations using a UI interface instead of a Yaml. The new UI should reduce friction points such as: Understanding the page layout and how to use different components Search for information in Port docs, to understand mapping and extraction capabilities. Search for information in 3rd party docs. Understanding Port’s Yaml structure Moving between tabs copying and pasting. (data model discoverability) Typos and syntax errors

By connecting remote MCP servers, like Notion and Atlassian, you can extend Port AI with more capabilities, tools, and data access. For example, ask, "Can you find the latest runbook for incidents in the API gateway?" which will rely on Confluence documentation.

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 customers to configure and manage SSO directly in Port UI without requiring support or customer success assistance. Proposed Solution: Introduce a self-service SSO feature that enables Port administrators to configure and manage SSO directly in Port UI without requiring support or customer success assistance. This feature should include native support for major providers like AzureAD and Okta, ability to test it before enforcing, and ability to apply additional provisioning like SCIM.

Support a Kanban board, allowing to drag items, etc.

Currently, the SCIM integration operates in the background to ensure secure access to Port. However, it is not fully integrated into the application—provisioning does not add users to Port, and deprovisioning does not remove them. Ideally, the SCIM integration should be fully implemented and seamlessly connected with Port.

Managing dynamic permissions requires specific skills and is more challenging to debug and verify. To assist, we want to provide an improved UI that will allow us to test the result and verify users defined the permissions as expected.

Embed the documentation directly in the integration-installation modal. This keeps users in flow, gives them step-by-step guidance without switching tabs, and helps prevent setup or permissions slip-ups.