Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,365,288
Community Members
 
Community Events
168
Community Groups

Best Case Scenario: Confluence Template Management

Edited

Let's say I work for the Acme Company, which uses Atlassian products. Acme wants to streamline processes so they can work more efficiently and at higher quality.

The product team has decided to standardize the documents used in their development cycles. They create five templates which they want PMs to use wherever they are in Confluence: Space Product A, Space Product B, wherever. 

Sounds like a job for global templates! These templates, however, have no value to anyone else creating documents at Acme. They now clog up the list of template options that employees see, which is a minor inconvenience.

Additionally, the head of product wants to update these templates fairly regularly, which means one (or several) people need admin permissions. Other teams have control and security concerns; unchecked admins put restricted pages at risk. 

As a happy medium, the Confluence administrator creates a group called "templater," which she applies to known product spaces and then gives space admin permissions at the global default level. This should allow a select set of people to add templates to any space. However, since there's no way to move a template, the product team is unhappy with the incessant copy pasta they're now required to initially do to have their templates available where they need them. 

The finance team has heard about this global template activity and would now like to place form templates in each department space that they can revise periodically.

======

Give me your best case scenario. How do you optimize this environment?

0 comments

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events