Feature ideas

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.

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

Ability to change organization name from the portal not just the API

Ability to change organization name from the portal not just the API

As a customer of Port, I want to access granular usage data of Port's features and user activity via API so that I can integrate it into my company’s BI system programmatically. This will enable me to create custom dashboards, monitor adoption and engagement metrics, and analyze trends alongside other business data sources.

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.

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

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

In order to prevent damage in an event of a leakage of an API key, extra security measures are needed. By whitelisting specific IP addresses for a Port organization, you reduce the impact of a leakage of API keys for an organization. Adding whitelisting in an organization level, and in an API key level will help protect customers' data.

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.