Feature ideas

Right now there is a 300 character count limit for the URL input when configuring an Organization Announcement. Many links are longer than 300 characters, and there should be no limit - or a far higher one.

This feature will make it possible to make a request to the access_token endpoint with a special flag, when a request with the flag is received, a new token will be generated (with a new TTL of 3 hours) even if an existing token is still valid

When an SSO connection secret expires, show a more informative and user-friendly error message instead of a generic “Something went wrong, please contact Port support.” The message should clearly explain that the issue is related to an expired SSO secret and guide the user to renew or reconfigure it. This will help users resolve authentication issues faster and reduce dependency on support for simple maintenance tasks.

Currently, users cannot be added to an existing SSO-managed teams in Port until they log in, even if they already belong to the team in the SSO provider. This creates a gap where team assignments aren’t visible in Port until the first login, preventing admins from ensuring that team data is complete before users start using Port.

Currently, the webhook secret and organization url dropdowns in the settings tab of data exporters are sorted nondeterministically. We request the secrets/URLs be ordered alphabetically to improve user experience when searching the dropdowns.

Enhance the icon library with a large number of different icons

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.

As a Port admin, I want to limit user session times to ensure there are no long-running sessions.

Currently service accounts must use the email domain serviceaccounts.getport.io . We would like the ability to create service accounts with our own email domain.

In order to improve adoption, key point is around branding, being able to use port ( even saas ) via a custom domain like port.mydomain.com , or dev-portal.mydomain.com can help tremendously on internal adoption