Feature ideas

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.

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.

Today you can only have one dashboard tab in the specific entity page. It would be ideal to be able to create multiple dashboards tab for different use cases

Currently, admins who add secrets are not able to see the value of the secret they're adding. In cases where they use this secret and get an unauthorized error, it would be helpful to see the text they are entering to ensure it is 100% correct.

Today a user that is automatically created using integrations / API is disabled by default, and the only way to activate it is by doing that for every user using the UI / API, and if a disabled user tries to login using SSO the user is blocked from access. Ideally, we would want the first SSO login to activate the user, without sending an invitation

Currently when creating a new property, there is a 30 character limit for identifier and title. Increase in the limit would be helpful.

Currently, validation prevents me from creating two dashboards/pages with the same name. However, this is a perfectly valid need for customers, who may want different personas to each have a "scorecard", "plan my day" or their own matching initiative dashboard page Even a UI option to create a new page as JSON would allow the differentiation of ids

In some cases, we may want to create a certain default value for a field based on previous selection made by the user. This can include literals and even multiple fields references. The default value should be adjusted automatically until the field becomes visible.

As an admin, I'd like to see the return status and body for webhook self-service action backends

Port Sender Github action can send scorecard notifications using slack_webhook_url associated with a specific channel. Requesting support for providing channel-id as input for github action to slack messages with same slack_webhook_url. Port Sender Github Action - https://github.com/port-labs/port-sender/tree/main https://github.com/port-labs/port-sender/blob/main/targets/slack.py#L4 Currently, it is using WebhookClient which allows posting messages using slack_webhook_url associated with specific channel - https://tools.slack.dev/python-slack-sdk/webhook Suggestion to implement WebClient, which will allow channel-id as input parameter for posting slack messages - https://tools.slack.dev/python-slack-sdk/web references : https://github.com/port-labs/port-sender/tree/main https://github.com/port-labs/port-sender/blob/main/targets/slack.py#L4 https://tools.slack.dev/python-slack-sdk/web https://tools.slack.dev/python-slack-sdk/webhook