Hi f2d42324e8dc.

What is the rationale behind having the page open in 'mode=global'?
It is really difficult to see the benefit of this and even harder to explain to our users why they have to do without the menu on the left.

Could you provide a bit more explanation on this? 
What do you suggest we do until this is fixed?

This issue should be addressed immediately in my opinion.  

We are experiencing the same issue.

Please assist to look into this.

Thank you.

Hi all — Appreciate folks raising this need. We do not have plans to prioritize at present, and we will change the status if that changes in the future.

It's been two years since my first comment on this.  We globally put a shortcut into everyone's bookmarks, but that's pretty hacky.  I guess we all just need to +1 this comment...  over and over and over...

is @nedlindau still active?

Atlassian you’re such a disappointment! I see new modules being released but no love is provided to your actual ones to make the user experience better. It’s pretty clear that this is a problem when you read the previous comments, all the admins get comments from their users about that basic feature. Also, that ticket as been opened for 6 years, what a shame.

This is important for us! We are about to move our intranet from Sharepoint to Confluence. That the default space opens in mode=global, with the lefte sidebar hidden, is a showstopper for us.

Chiming in here - we also had to move to a cloud instance and this is absolutely annoying! We run a public instance (mainly to showcase our app(s)) and this is completely messing up the user experience. PLEASE implement this! It can't be THAT hard, right?

Starring/Watching is NOT an alternative, we want to have a LANDING page with a decent user experience.

Dear Atlassian Developers,

why is it so damn hard to integrate this feature to implement a checkbox which, when activated, changes the URL to not include "?mode=global"?

Looking at this issue and a lots of questions when googling it, clearly states that this is something almost everyone needs and wants. 

Could you at least state, why you are not going to implement it? 

Please fix this ASAP. Hundreds of user in our organization complaining about this

Hi, this is affecting my entire 300 user base. We just migrated from on prem (Server) to Cloud and none of us noticed this issue until after we completed the production migration. Now I am dealing with a large number of users who are bewildered as to why the sidebar won't appear (and once they do make it appear why it won't stay open). Last resort has been to tell users to remove the "?mode=global" after the browser loads the page.  This is not a great user experience. I don't see why this isn't a higher priority issue since it affects 100% of users. Atlassian, please up the priority of this!

This is the first thing I noticed now when playing with Confluence Cloud. Which is just annoying, luckily we are not hooked to confluence yet.

We migrated from the server one year ago. Hard to belief that there is no action taken for this issue. 100+ people suffering in our organization.

When you migrate from Server this is a mess. Please enable the sidebar.

Something claimed by a lot of users..  And something very easy to implement. I do not understand why they did not implement neither give an explanation why not..

Same boat here.
We also came from DC on-prem and were searching for a solution to this. Our users want the sidebar visible.
Anyone with a workaround?

Having moved from the on-premise, self-hosted Confluence to the Confluence Cloud version, this has been the most requested item from our users.

Removing "mode=global" seems like an easy change that would make a lot of people happy? Bumping this.

Please provide an update on this. Showing no sidebar makes no sense on the homepage.

It's july 2023 and still no solution....

Seems like an easy fix for a quick win for alot of confluence users

This blows our mind too.  Not sure what the developers are thinking or why this is not a common sense priority.  Why did they even create a global mode like this if you can't edit the option.   What a a pain for our users.   

Moving from Confluence self-hosted to Confluence Cloud, our users noticed this right away and I'd definitely like this feature to admin control a setting for this in Confluence Cloud. 

Why hasn't this been fixed seems like a quick fix. I'm also not really happy with the migration to cloud as I'm loosing some customization and features.

So far pretty disappointed with migration to cloud and loss of features

Yeah this is super annoying. What is the global mode used for anyway?

That should be easy to fix and would be so useful for all the users!

Matt-Reynolds,

save your breath, there will be more issues to discover with cloud version ... sad but true ... :-/

Just started the trial migration from on-premise, and found this bug.

How has this been open for FOUR years and not been fixed yet??

Is this one so hard to fix? Unbelievable! Please do us a favour and make it changeable, thanks.

When configure the home page is there a way to use or use not the global mode with checkox? Thats where a nice feature

How the hell this still unfixed?

Thank you @Vitor for the reference. Please work on this ASAP as a significant feature request?
We're in the process of migrating our confluence server and this very much changes our user experience on first login.

Alternately, Your team could give us the ability to specify a unique page and not just the space itself when setting a custom homepage.

would be great to be able to see by user group. Content creators should have the side bar,  normal users should use global mode.

Please fix ASAP. Totally agree with everyone here

add another one for vic's comment.

+1 for the issue and Vic's comment.

Please start thinking from a (new) users point of view.

+1 for the issue and Vic's comment. 
We're using a dedicated Cloud instance for a public product documentation. There is a full page navigation in the sidebar. Whenever people navigate back to the site home page the sidebar vanishes, causing lots of confusion. 

100% agree with Vic Breen's comment, thank you.

👍 on Vic Breen’s comment. Thanks!

I'm just going to freely and openly rant here.

Pawel's answer is not a workaround at all, it's adding unnecessary steps for the user. Disabling redirection and sending the user to the list of spaces adds an extra step that didn't exist in the Server product. The "this is by design" answer that I've also heard from Atlassian directly via a ticket is just the most awful response to a simple fix to a simple problem. I'll bet anyone a ham sandwich this could be implemented in less than 20 minutes and a few minutes of code review. Add a toggle option for "mode=global" on default redirects so it doesn't get appended to the URL at all. Done! Everyone watching this ticket would be instantly happy.

My customers currently just go to our base URL on our self-hosted Server (license soon to expire) and they get presented with the single public space we make available to them. No clicks, it just works and they can see the sidebar. No complaints whatsoever.

Forcing the customer to look at a list of one space item, to then have to click on that single item to get access to the same information that used to just be presented on the first visit is just plain stupid, IMO. This "it's by design" argument that I've been told by Atlassian tells me they don't care or never even bothered to understand anybody's use case for having a self-hosted product.

Atlassian has forced us away from a perfectly satisfactory self-hosted product we were happy to continue to just hand over a yearly license fee for, and pushed us over to a cloud hosted product that has less and broken functionality. Just because something is hosted in the cloud doesn't make it better or "the new hotness," and this is a clear case of that. If we weren't force to do this migration, I'd call it buyer's remorse, but I can't come up with something better than that to describe how sour this migration experience feels based on just one small stupid broken detail.

How many more votes do we need on this issue to get this moved out of "GATHERING INTEREST" and into the dev pipeline? 3 years and no traction? Just incredible.

Workaround is to disable redirection to speciific Space and make it so it shows all of the spaces. Then if the user clicks on one it works properly with the sidebar.

In my support case, Atlassian claims this is "expected behavior", even though it didn't used to function this way for us:

"This is the expected behavior - the Space sidebar is not displayed, because the users are not accessing the Space - they are on the Instance's homepage. When they access the Space the sidebar is still visible.

in case you don't want to use a Space Overview as your homepage, you can set it as the dashboard, which you can access on https://<site>.atlassian.net/wiki/home

You can have further information about the Site Homepage on this article.

I would also like to add, that we've released a new navigation experience last year. Before this improved top navigation bar, you could find a sidebar when accessing your Instance Home, but the sidebar wouldn't be the Space sidebar - it had the same options available on your current top navigation bar, such as - Spaces, Recent, Apps, and Settings (the visibility of these options depend on your access level)."

I don't understand why they can't make this an option and let the users decide how they want their sites to work, instead of forcing their logic on everyone.

How about adding a exand option for the sidebar as is done normally when the sidbar is collapsed?

@Joe Bloggs: It used to work fine, meaning the sidebar was displayed, and then one day it stopped working.  Seems like a bug to me.

@Michael Willers: Since they are still actively working my case, I'd rather not halt any progress.  If other users open support tickets, it might help with the investigation.  

could you reference this issue in your support ticket?

I thought this was a bug with our Confluence site, so I opened a support case.  I've provided screen shots, descriptions of the behavior and a video, but Atlassian states they can not reproduce, even in our instance of Confluence.  This is strange because it happens to every user in our site.  Perhaps if others here open up support tickets it will help? 

Hi agree, this is awful can be fixed please.  @Jeff Hoover, definitely not a bug, but rather default behaviour? 

This behavior is absolutely bizarre and I don't understand the reasoning behind not being able to configure whether "?mode=global" is tacked onto the end of the URL or not. This behavior didn't happen at all on the Server product, and now that I'm unable to use that product moving forward, I'm forced to use what I consider an inferior and broken Cloud product.

This weird hiding of the sidebar behavior makes zero sense, like absolutely none. The sidebar is a critical piece of navigation with a space that you're intentionally obscuring for what reason, exactly?

I'm even more discouraged by the fact that this issue was opened in 2018 and we're now solidly into 2021 with this issue still "gathering interest".

Please add this request to your development pipeline. I'm sorry this post is such a rant, but it's frustrating to see how simple the solution is without having a simple "knob to turn" to change the behavior.

very annoying, inconsistent behaviour

Please fix ...