Feature ideas

With the introduction of Multi-org, session tokens are now shared across browser, preventing users from being able to simultaneously work in different environments. Allowing for multi-session support where users can work cross-functionally across different environments would help restore this previous workflow and alleviate pains experienced in platform where sessions refresh and potentially switch orgs in the current active window, leading to improved user experience.

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.

The login from Port's main website routes to the EU tenant login without any indication to users of such. This is resulting in our employees finding your sign in, and logging into the wrong tenant and being confused. Please update your website to allow selecting a tenant to connect to.

Problem description: The "Refresh" (rotate) and "Copy" buttons in the Credentials/Secrets modal are placed too close together, causing users to accidentally trigger a secret rotation when they intended to copy the token. This has already been reported by multiple customers and has impacted entire organizations by invalidating active secrets without warning. Current behavior: The rotate secret button and the copy button are adjacent, with no sufficient visual separation. Although a confirmation dialog exists after clicking rotate, the proximity of the buttons makes accidental clicks easy — especially for users unfamiliar with the layout. Expected behavior / proposed solution: Either of the following improvements: Increase the spacing/separation between the "Refresh" and "Copy" buttons to reduce accidental clicks. Add a more prominent confirmation dialog with a clear warning before executing a secret rotation (e.g., "You are about to rotate your secret. All integrations using the current secret will stop working. Are you sure?"). Impact: Accidentally rotating a secret invalidates all active integrations and automations using that credential across the entire organization, requiring immediate remediation. Related FR: This is related to the existing FR: User approval when doing Client Secret rotation [User approval FR]

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

We want to be able to create a new org in our multi-org structure using the API and not the UI in the app.

With multi-org, people often share port urls with others who are not in the same set of orgs. It would be useful to be able to specify which org should be opened when sharing a url.

Request for the ability to upload custom logos that will then be available in all orgs in the multi-org account. Currently, you have to upload the same logo in each org individually. It would be more convenient if they sat at the account/company level.

Fetch's org model is Collective → Pack → User. Attached screenshot showcases Fetch's existing hierarchy view on Port. Requested is a single hierarchy view where: > Collectives expand to show Packs (currently possible) > Packs expand to show Users (currently not possible) > Ideally in the same view (org‑chart style), not separate tables or dashboards. Goal is to support resource‑management and team-reallocation scenarios (seeing who sits in which Pack under which Collective) in one view. Currently using an internal tool 'Celestials' for this and aim to replace it with Port.

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.