When will custom stylesheets be permitted again? One for light mode and one for dark mode. I can modify with Stylebot plugin but that only applies to my view, I'd like to be able to customize our Confluence instance again.

I use custom styles extensively to ensure all aspects of the site are accessible and compliant and the lack of this ability is hindering our ability to be ADA and 508 compliant.

If you are looking to customize your Confluence display to better match your corporate branding, Spacecraft could be a good option. It won't give you all the flexibility of custom CSS like on Server, but you can easily add backgrounds, custom headline font, and hide UI elements like the native top navigation bar (with the Templates and Create buttons) and the Space Setting link.

I completely agree with @KoheiMashida. As we migrate from a server instance, the absence of customization options is sorely felt (the same applies to the JSM portal).

There's more to consider beyond just branding and design capabilities (But those are obvious).
From my experience with server instance, the ability to selectively hide certain UI elements, because many are displayed but ultimately inaccessible due to permissions, has significantly enhanced the customer experience.

Please ...

Having water mark with our company logo and login user will discourage users from distributing restricted contents to third parties.

As we move forward with cloud migration, the fact that this functionality has not yet been achieved is a major obstacle. Not being able to do things that they used to be able to do is greatly reducing user satisfaction.
I hope this feature will be implemented soon.

I'm with Helen here - the excess white space and inability to edit any CSS is so amateur but we have to pay professional prices for this?

SFDC and Zendesk are light years ahead of Atlassian when it comes to Help Centers - I was about to upgrade to Premium for Confluence, now I'm questioning JSM as a whole.

I've avoided the new editor until now, and have kept hold of the legacy editor...  Unfortunately, Atlassian have introduced a bug that has totally broken links in my legacy editor pages, and I am sadly now a new editor user.

And it's awful... So awful. One of my main issues is the excess of white space — why? why? why? — and huge font size.

(Other issues relate to some of the macros not working as they did in the legacy editor — they have reduced the functionality of the excerpt macro and the way images can be edited. Again, why?! But that's a rant because all my requests for help with these have been ignored elsewhere )

I really, really want this css capability.  The tables as-is are useless for so many tasks due to SO MUCH padding.

Insult to injury:  the greyed out option to turn this on makes it look like a admin-permissions issue.  2 of us battled that for a while.  What a waste of time.

I am increasingly disheartened by the ongoing poor decisions, such as the inability to read long texts in Confluence Cloud due to the line spacing (margin) and the 8px padding in tables.

I also believe that the cloud is misunderstanding customer metrics. It's concerning to see a pattern of decisions that seem to alienate loyal customers in favor of attracting new ones.

Branding is important to companies, and hence allowing us to put in custom CSS to standardize our Confluence Knowledge bases/documents would also be important!

I understand you are working on ways to allow customization via the actual user interface (within the template itself as in possibly adding a custom color picker and a variety of fonts–which is normally contained in most applications and so seems quite straightforward to implement).

However, in the meantime some of us are creating templates and the delay in waiting for this upgrade will cause us to have to go back in a few months, re-create the template and then re-port all the content into our branded pages. 

Is there any way in the interim you could re-activate the custom CSS? I really prefer not to have to re-do a few hundred pages of content because I was waiting for "the better thing." Thanks!