Add option to stop hub sites forcing themes on associated sites
As much as I like the concept of hub sites giving a common theme and navigation across associated sites, sometimes (quite often in fact) I'd like the associated sites to only inherit the navigation and not the theme itself.
I have a department that uses our company colours for each of their teams within it. I have SharePoint theme's of our company colours, but if I group them in a hub I lose those themes. Or I don't associate them lose the navigation across them.
All I'm really asking for is an option to not inherit the theme. Or I suppose I'm using themes wrong based on the narrow scope they were created for?
Mark Owen
shared this idea
24 comments
-
Anonymous
commented
Is there any official comment from Microsoft on this topic? My customer needs this featue to take care of two different brands.
-
Andy Clapham
commented
Seems like a silly misunderstanding. A hub is supposed to bring together different sites under a common umbrella, not work just like subsites. Yes the option to cascade styles might be useful, but the option to *not* cascade styles should be there by default.
So many illogical aspects to SharePoint, no wonder nobody really likes it. I seem to spend half my life trying to explain why we're not going to buy confluence + dropbox + smartsheets + trello + slack + zoom + yada yada and that we already pay for MS365 which does all that... only for people to be so let down by the experience that I feel like I'm holding them back from realising the potential of all of these tools.
-
Anonymous
commented
With 3 brands to manage this is a must have feature.
-
Anonymous
commented
Yes, we desperately need this functionality. I have 7 sites we want to add for the enhanced search functionality, but cannot change their designs.
-
Anonymous
commented
This is really needed. I have 7 older sites that have developed the own themes. I want to make a site a hub site for search across sites. However, I am unable to implement this if the hub site keeps changing the subsites.
-
Muhammad Waqas Naseer
commented
I think you can change the theme color of Associated site independently By clicking "Change Site Look" and then at bottom you will see "classic change the look options" from there you can click on a theme and then select your required theme palete from the menu.it works for me. Hope it works for you too. :)
-
Ashley
commented
Has been over a year now. When will this be looked into? We really do need the ability to have associated sites excluded from inheriting the hub's theme. Having ability to do via PowerShell would help as a first step.
-
Anonymous
commented
I couldn't agree more!
-
Kiley Ohl
commented
While it is a good principle by default, we are now thinking we want different theme colors for certain vertical functions, but like the idea of a common global nav that is security trimmed, as well as the benefit of cross populating news, events, etc. to a few key communication sites with little effort. Agree - this is something that should be easy!!
-
Anonymous
commented
Why is this even an issue?
-
Richard
commented
This seems like it would be so easy to implement!
-
Rich
commented
This seems like it would be so easy to implement!
-
Anonymous
commented
This is a must to have.
-
Corey
commented
Just ran into this problem. Quite annoying this isn't an option.
-
M.E
commented
Need this so bad, hurry up
-
Anonymous
commented
This is so ridiculously needed.
-
Malik Noentil
commented
I also have the same set of requirements. Though each site collection is associated by a hub site, they should be independent enough to chose a theme of their own.
-
Uros
commented
I agree.
And on a side note, the UserVoice system seems to be quite inefficient and unfair. If something has under a certain amount of votes it feels as if it is immediately ignored by Microsoft? What are we supposed to do have an army of bots vote on our issues?
-
Benoît Fournier commented
I have the exact same need.
-
Veronique Palmer
commented
I agree too, we need more flexibility on this
