Thank you everyone for your suggestions on the template editor - as we've been working on creating the best template experience for the community, this is not a direction we will be able to take right now for the overall creator experience strategy! We will definitely keep these suggestions in mind for future projects and appreciate the feedback. Please feel free to check out some of the brand new templates that we have released in the last few months here! 

I think the admin should have the privilege to force an editor for a whole workspace and not the users who may find one of the editors more comfy to use than the other, but also compromise the unified look&feel of e.g. Product Documentation products. That should not be the decision of the user (since the two editors have very different capabilities).

Also, the admins should be able to restrict the users from creating their own templates OR to use any template willi-nilly. For a Documentation Space the look&feel is very important, even on information structure level. If they start using their own stuff, that would mean a hude overhead on correcting everything before we publish a product documentation to go with a sw release. So I don't mind if ppl have their own templates, just the right to use them in a certain workspace or a certain section of the workspace - should be in the control of the space admin.

Note that to complete support for the Legacy/Old/Complete editor, item https://jira.atlassian.com/browse/CONFCLOUD-69945 (add the ability to create templates using the legacy editor) is also needed.

My preference is to default ALL pages back to the old editor.  But if not, at least this makes it more likely users may pick the template I want them to use.

@Sattesh Maran

Please update this request to reflect more accurately the ask. We would like to set the default editor at the instance level, not just for a specific template.

As admins, we should be able to set the default editor used by the instance for all pages/blogs being created. As a  user, I should have the option of setting my personal default within my profile.

@sattesh, Can you please update the Summary if this issue to better reflect the "ask" - Allow Confluence Admins to configure the "default" editor for their instance. 

As an Admin, I should be able to set a default editor so my users do not have to search for the Legacy page template every time they create a page.

Atlassian has stated that the Legacy editor will not be "going away". Given this fact, we should be able to set the editor we would like to use as the default.