Forum Discussion
SharePoint gear icon changes
Update (Apr 8, 2019): Please vote for this idea, if you face similar issue
What happened to settings menu?
I'm a site collection admin and suddenly started noticing different options and different UI on Gear icon but it is working fine with Read only user account.
Note: I'm also in Targeted Setting and we are using classic site.
Look at the difference in the screenshots. It changed the top orange bar and new options !
How can I have the same Orange top bar?
How can I get the old user experience?
What is this Themes? How can I create a custom one that changes the top bar?
My View:
Read user's view:
I think this link maybe help you.
https://techcommunity.microsoft.com/t5/SharePoint/SharePoint-Online-Settings-menu-change/td-p/357012
- This was posted in the admin center over s month ago. The changes are to the suite bar so it’s going to effect classic and modern and there is no way to change it.
The orange is just a different theme most likely under all themes.Thank you ChrisWebbTech
It is custom orange color that aligns with our brand.
Andy TischaeferMicrosoft
Mahendran D Hi. I'm the engineering manager for the common O365 suite header and wanted to try to address your concerns.
I'll start with the good news - the suite header respects tenant-wide theming as set by the tenant administrator. You can set up your color scheme there and it will be consistent across SharePoint and most other O365 web properties. Tenant admins also have the option to restrict individual's access to custom themes, which will make the theming panel you see above shrink down quite a bit (we always offer a high-contrast option for users). You can find the options for both of these things in the O365/M365 Admin Center.
The bad news is that the new suite header does not, today, respect SharePoint-specific themes as set in "Change the Look". We're opting for suite-wide consistency over site-specific customizations here. We of course want your feedback on this. We have seen several customers raise concerns with it already.
Now I'll provide a little more context for the changes, in case it helps.
The recent changes to the suite header do two things. First, they move the underlying code to a modern, forward-looking codebase. This brings with it a much easier servicing model, better performance, and makes it cheaper and safer for us to introduce new suite-wide capabilities to Office365. But that's all "under-the-hood" stuff.
The second and more immediately impactful change is our attempt to bring the entire O365 suite in line to the same (or very similar) header experience. Prior to these rollouts, different O365 apps had considerable differences in their implementation and display of header features, SharePoint being the biggest outlier. With these changes, we're attempting to find the common ground between O365 suite-wide consistency, user personalization, and app-specific needs. We may not hit the mark perfectly each time, though, so it is important to us that you keep providing feedback. We do listen and your comments do inform future decision making.
Thank you.
