Feature ideas

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

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.

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.

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.

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.

Currently, port do not support dynamically re-reading secrets attached to Ocean custom integration. This is already supported in Other Ocean integrations in the following way: Ocean has a built-in mechanism: when this parameter is set, any 401 received from the third-party API triggers Ocean to re-read the token from that file and retry the request - assuming the token has already been refreshed and rewritten there. This allows us to assign external secret and the Ocean integration will use it correctly when rotated outside of the integration. Port should extend this to Ocean Custom integration to work the same way to allow for short lived tokens needed in some APIs.

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.

Enable users to validate integration setup before full installation by testing connectivity, access, and basic permissions. Reduce setup errors and improve user confidence in integration correctness during onboarding.