Hello everyone,

We are currently shifting the efforts from templates to additional customization options for Confluence Cloud. However, this suggestion is under the team's consideration, meaning that even though our work for implementation is paused, we might come back and consider implementing it in the future.

We will still keep the maintenance and continue to fix bugs that have higher priorities as per our Bug Fixing Policy.

Thank you for your understanding.

Wish you the best,
Giuliano C.
Atlassian Team

I have this problem as well. I am using the Scaffolding plugin from Service Rocket and the Live Templates that are the source should not be selectable. At this point I have had to cryptically name thema nd put DO NOT USE as a description. Pretty ugly solution.

When running Confluence for a lot of years you probably have created a lot of templates. Some of them might be live templates using the Scaffolding Plugin. A huge amount of historical pages are based on them. If you decide to remove such a template, those historical pages are not displayed anymore. They have "lost" their contents due to the Template is not accessible exception.

If you do not remove those old templates, people tend to create new pages from them instead of using shiny new blueprints or different templates.

This blocks both process and creativity and leads to frustrated people in a corporate environment.

Please, make it possible to hide certain templates from the list of available templates.

My use-case is quite simple. I want to clean up among all the global templates but I don't want to delete them because I'm not quite sure which ones I want to keep yet.

Blueprints can be disabled, but why not templates?

We use SQL code in some Global Templates (live templates) that are used by other pages to display data. These are not useful to end users to create on their own and it would be nice to hide them.

Out company is large and very heterogeneous. On the one hand the users ask for structures like templates on the other hand the demands are very specialized. When creating global templates I more or less give recommendations how to structure a page. But each department likes to have some addons to the global structures which are quite individual. Their way is to duplicate that global template and to create one with their own specifics. Keeping the global templates helps new born spaces to adhere given structures for cross-space benefit but as soon as they discover self-created templates they like to "replace" the global one by deactivating it. As soon as they mature in using wiki they have to handle multiple templates where half of them won't be used in their space but still shown. From their perspective this is not focused to the essential as the rest of the wiki seems to realize though.

I have the same use case, Live Templates should not be viewable to the end user.

A combination of the Scaffolding plugin and live template has a strong requirement of hiding a base template from the user so they cannot select it.

Does anyone know if Blueprints might address this at all? It seems quite a simple request, but then again, nothing is easy.

We have the same use case as Anthony and Anita above.

Scaffolding bridges the Gap of Multi-page Templates etc that Confluence doesn't offer but as a result we have all these child templates that we want scaffolding to be able to access and use but the actual user doesn't need to see them or select them.