Hello there,
I’d like to share links to a dashboard on tenancy B, but the default tenancy for everyone is A. So when the receiver receives the link this is what they have to do:
Is there a way to skip the third step, by putting the tenancy in the URL somehow, so that the flow can be smoother ?
Good point! We are going to implement this. We will reach out to you with a pre build to test the feature tomorrow tops.
Thank you for your reactivity!
Unfortunately I’m not admin of our instance and am not in a position to try anything out. However if this makes it in the next version I’ll make sure push to include it !
@Matthieu I forgot to follow up on this, sorry. It has been fixed. The syntax to send someone a link to a specific tenancy is the following:
If you want to show this link https://kibana:5601/some/dashboard using this tenancy tenancy1, you send this link:
https://kibana:5601/switch-group?group=tenancy1&redirectTo=https://kibana:5601/some/dashboard
This link will take the user to a login page if necessary, and then switch tenancy, and land into the desired dashboard.
The above works with ROR Enterprise >= 1.35.0 (to be soon released)
@sscarduzio Amazing, thanks for working on this. That will be extremely helpful !
Very happy to help, @Matthieu! 
Hello @sscarduzio ,Is it possible to include https://kibana:5601/switch-group?group=tenancy1&redirectTo=(actual short url) in short url when user clicks on copylink in kibana ,modifying url may be a additional task for user
Hello @mgopathi01 interesting, but I’m not sure I fully understood the user story you have in mind. Can you spend a paragraph on giving some context, and step by step desired user interaction vs current behaviour?
hello @sscarduzio ,
Sure, let me clarify the use case.
Current behavior:
User A is working in tenant1 and creates a dashboard short URL using Kibana’s Copy link / Short URL feature.
User B is currently logged into tenant2.
User B must manually switch to tenant1 and then reopen the link.
Existing workaround
As suggested earlier in this thread, the link can be manually rewritten as:
https://kibana:5601/switch-group?group=tenant1&redirectTo=``<actual_dashboard_or_short_url>
This works, but requires manual URL modification, which users often forget.
Desired behavior
When a user clicks Copy link / Create short URL in Kibana,The generated URL would automatically include the tenant context
(for example by wrapping the short URL with /switch-group),So that recipients are transparently switched to the correct tenant.
Is something like this technically feasible or planned?
Yep this is extremely useful, we should explore how to do it. Thanks for bringing this up.
Created an internal ticket for this. Will brainstorm with the team on what’s the best way to go at this and let you know.
Hello @sscarduzio, thanks — one related usability issue we’re seeing is working with multiple tenants in parallel in the same browser.
Tenant selection appears to be global per browser session, not per tab.
Example:
Tab A is set to tenant1
Tab B is set to tenant2
Returning to Tab A, interactions stop working or, after refresh, the tab is implicitly switched to tenant2
This is confusing for users and can lead to dashboards or searches being created or modified in the wrong tenant.
Our users frequently need to:
Compare dashboards and metrics across tenants
Copy or validate content side-by-side
This naturally leads to multiple tabs, which currently isn’t safe.
I noticed this fix in the changelog:
“Resolved an issue with CSRF token override when multiple browser tabs were open”
Does this also address tenant isolation across tabs, or is tenant selection still intentionally global per browser session?
Could you help to clarify, thank you !
BTW, since its a follow up on link sharing issue ,i used same thread let me know if you want me to start new thread.
Hello @mgopathi01
Does this also address tenant isolation across tabs, or is tenant selection still intentionally global per browser session?
Yes, however, it’s not related to the browser session, but rather the user session (which is global for a specific browser, because of cookies). At this stage, the only way to handle your use case is to log in to a different browser/incognito mode.
However, I will discuss your use case internally with the team.
@mgopathi01 the share link has been taken under development, I’m about to add the per-tab tenancy feature now to the sprint.
By the way: the per-tab tenancy is one more gem! Thank you for proposing these excellent improvements, I can tell they are coming from real power users. And I’m sure a lot of ROR users will immediately benefit from these. So keep them coming 
By the way, may I ask you a favour: can we have one fix/feature request proposed per forum topic?
Also, thanks for using public topics even if you have direct private message access (as an Enterprise user), you keep our community engaged while your case priority remains high because you are marked as an Enterprise user.
BTW Maybe not everyone knows, but when someone posts in the forum using the same email used in the portal, the support team knows the priority level, even when writing they public threads.
Thanks a ton @sscarduzio really appreciate quick actions.
per-tab tenancy picked up sprint is great news.This use case really comes from multi-tenant work flows.
Noted on keeping one request per forum topic ,will do going forward.
Thanks again to you and to the team.
Hello @sscarduzio
Just checking in to see if there’s any update on the per-tab tenancy feature and link sharing feature that was planned for the sprint.
Really looking forward to it.Totally understand if it’s still in progress , just wanted to follow up.
Thanks for following up @mgopathi01 both per-tab tenancy and link sharing are being taken care in the same PR, as the two features are very much linked.
We are introducing the selected tenancy name as part of the URL, the url shortener in Kibana will take care of preserving this information automatically.
If the recipient of the link will not have the permission to access such tenancy embedded in the link, an informative 404 will be shown.
The PR works, @Dzuming is writing some tests. Will check with him.
Just heard back from @Dzuming - will be ready on Monday!
The plan is we give you a pre-build so you can test it, then you will see it in the next release.
Hello @mgopathi01 ,
What version of Kibana do you use? I will prepare a pre-release build for this version.
Hello @Dzuming , Thats great ! to be able to test could you please update docker image with latest ror version beshultd/kibana-readonlyrest:7.17.24-ror-1.67.3