Multi-session Support for Account Organizations
complete
B
Bill Gilleran
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.
Guy Berman
marked this post as
complete
Great news - this is now shipped!
We've released Multi-org support, parallel sessions, and deep links in General Availability, and it directly addresses everything raised here.
What's changed:
- Isolated sessions per tab - Each browser tab now maintains its own independent org session. Switching orgs in one tab will never silently affect another. The "Your active organization has switched" popup is gone for good.
- Deep links with org context - Port URLs now include the org identifier in the path (e.g.port.io/org_1234/…), so shared links always open in the correct org. No more 404s because a link landed in the wrong organization's context.
- Org-aware tab titles - The address bar and tab title both reflect which org you're in, making it easy to tell staging from production at a glance.
Backward compatibility:
Existing links without an org in the URL still work - you'll land in your last-used org, same as before. No broken bookmarks. we do recommend you to update your existing links/bookmarks to be org-scoped to avoid any unexpected behaviour.
This should fully unblock the staging/production side-by-side workflows and shared-URL reliability issues described in this request. Let us know if you run into anything unexpected!
Read more in the docs - https://docs.port.io/sso-rbac/multi-organization/#organization-aware-deep-links
Dudi Elhadad
marked this post as
in progress
Dudi Elhadad
Merged in a post:
Feature Request: Organization-Aware Deep Links via URL Parameter
L
Linas Daneliukas
Problem:
When a user receives a direct link to a resource in Port and is not currently logged into the target organization, they are presented with a 404 error — even if they have valid access to that organization. This creates a broken experience for link sharing across teams and stakeholders.
Proposed Solution:
Introduce an organizationId URL parameter that allows links to specify the target organization explicitly. When a user lands on a URL containing this parameter, the app should automatically resolve the correct organization context before rendering the page.
Example
With this feature, a user who has access to prod but is currently logged into a different organization (or is not logged in at all) would be seamlessly redirected or prompted to switch to the correct organization — rather than hitting a 404.
Dudi Elhadad
Merged in a post:
Org-Specific Context Handling for URLs in multiorg set up
k
kumara gurubaran
Request to enable shared URLs (for example, to an SSA or dashboard page) to explicitly target the correct Org context in multi-org environments.
When a user opens a shared URL, they should be automatically switched to the correct org (assuming they have access to it), rather than loading the page in their last visited org.
Currently, shared URLs always resolve within the user’s last active org. In cases where the referenced resource exists only in a different org, this results in a Not Found error, even though the link itself is valid.
Ideally, this could be supported via an org-specific query parameter (e.g. orgId=...) or equivalent mechanism to ensure deterministic, org-aware deep linking in multi-org setups.
Dudi Elhadad
Merged in a post:
Allow working in multiple Port organizations simultaneously across browsers
K
Kevin Puventhiranathan
Today, with multi‑org enabled, a user session is shared across organizations. When I log into different orgs (e.g., staging and production) in separate browser windows or even different browsers, Port will automatically switch the active organization to the last one I logged into. This causes my other window to prompt for an org switch and reload into that same org, preventing me from keeping staging and production open side‑by‑side for comparison or safe configuration changes.
I’d like the ability to:
Keep multiple organizations open at the same time (e.g., staging in one window, production in another, even across different browsers), without automatic cross‑window/org switching.
Ensure that org context remains stable per browser window/session so that a page refresh does not silently move me to a different org.
Especially pertinent since switching a lot between staging and prod and using multiple tabs, the local state stored in the browser can get out of sync with the actual layout definition in Port. When that happens, a different widget arrangement may be shown, while everyone else sees the correct layout.
Photo Viewer
View photos in a modal