Feature ideas

Within our organisation, we have a convention whereby all Entra security group names follow the format Team_[Name_With_Underscores] . While this convention works fine within Entra, when it's exposed in Port (e.g. via SSO & group claims), it can lead to some minor UI issues: Team "avatars" all start with 'T' - the chances of multiple teams having the same abbreviation is much higher (see attached) Team names aren't user friendly - particularly to non-technical individuals The suggestion here is to allow Port admins (or team blueprint moderators) to rename the entities - i.e. change the $title value, while still maintaining the connection to the underlying SSO group.

Enhance the icon library with a large number of different icons

When "Continue with Google" is on the login page, users who use Google Workspace for SSO might be confused about how to log in. Some may end up clicking on "Continue with Google", which should not happen when SSO is enabled.

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.

The create-an-access-token API currently uses clientId and clientSecret as parameter names. To improve compatibility with OAuth 2.0 clients, to enable support for the standard parameter names: client_id and client_secret.

OpenAPI specifications make it really easy for developers to start using API endpoints. If Port were to publish such a specification for their own APIs, this would make it much easier to quickly spin up adhoc requests for experimentation.

Today when you type in a field related to sensitive inputs (for example, a new secret used for Port hosted integration), the characters in the field are shown as dots to mask the actual value. It would be very helpful to have a "reveal" button that will show the actual value after typing, it could help prevent typos or input mistakes

Currently, time-based configurations require manual updates when daylight saving time (DST) changes. This feature request proposes an enhancement to enable the system to automatically adjust for DST without requiring manual modifications. Implementing this would ensure accurate time calculations, reduce the risk of errors, and eliminate the need for repeated adjustments.

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.

When I go to "credentials" tab I see secrets values, it may be a critical point when I work this and share my screen. I would be nice to hide the Client secret value by default (both Organization and Personal), make it blurred or something