Feature ideas

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

Sometimes there is a need to create multiple Port "Workspaces", for example, for staging and prod versions of Port. We would like to add the ability to create several workspaces to an organization and to be able to easily switch between them via Port's UI.

For customers who work with 2 environments - we need to have a fully automated deployment process that enables changes made in the staging environment (particularly those made via the UI) to be automatically or semi automatically pushed to the production environment.

As a Port admin, it would be ideal to be able to rotate the Kafka topic password for security purposes

I would like to be able to manage secrets through Terraform, this will also make it possible to use automatic rotation.

Implement functionality to fully customize the invite email when you invite a new user. Should be able to change the contents of the invite link in the button and actual text.

To enhance the security and isolation of our data handling processes, a dedicated Kafka queue will be a necessary feature.

If I have two port instances for my organization (i,e - dev port, and prod port), I should be able to replicate data across the two instances so that I can use live data for testing changes in a lower environment instead of having to use production for the live data.

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

Currently, the only way to determine what groups will be synced with Port is by creating REGEX and sending it to the Port team to implement. We would like to have the ability to easily control the groups' allow list via Port's UI/API