How to create a table that can be used as a template, and cascade updates?

[Kelly Brussel]

I would like to create a template, perhaps a database or some kind of table, that can be shared to different teams for their customizations. here is an example:

Template Document/Database X houses questions 1-20. 

Questions 1-10; owned by a centralized team A, who updates Database X

Questions 11-20: owned by separate teams B C and D, need to provide custom answers 

I want all teams to be able to import the template/database and, on their own pages, answer questions 11-20 without affecting the main/template database. 

But I want the main/template database X to cascade updates to those teams, i.e. if an answer to question 1-10 changes, or if Team A adds a question- but changes made by teams B/C/D cannot cascade backwards/upwards to affect the main/templated document 

Does that make sense? Is this possible? I am starting by creating a database, but unsure if this is the right solution and/or how to proceed. 

[Tinker Fadoua]

Welcome to the Atlassian Community @Kelly Brussel !

How about creating a Global templates without the use of Database in Confluence?

Your teams will create page using one of the templates, and the original ones will remain unchanged so they can be used any time.

Does it make sense? Below is a doc from Atlassian with all details

https://support.atlassian.com/confluence-cloud/docs/create-a-template/

Let me know if you have any questions

Best,

Fadoua

[Kelly Brussel]

Hi, thank you for the suggestion! If the owner of the template modifies it, will that change cascade to the pages made with the template? 

[Tinker Fadoua]

Hi Kelly

Unfortunately any changes to the template will only apply to newly created pages. They won’t apply to existing ones. 
Best

Fadoua 

[Kelly Brussel]

Thank you! I'm not sure that would work, as we need something that would automatically update for anything the central team changes. Here is an example- a source (centralized database) that has shared Q&A from a central team, then templated questions that each team need to complete for their own units. If the owner changes anything in the centralized space, those changes would update accordingly, and if they add something new, it would also update.

Essentially we want to guarantee that different teams are building consistent knowledge bases that will not get out of alignment.

Hopefully that makes sense and might be something we can build.