# Amazon Quick adds centrally managed brand templates > AWS says brand templates are generally available in the Quick desktop app, with administrator controls over who can create and publish them. Canonical URL: https://www.devobs.io/news/news-event-026a9be200c14e0975481c09/ By: Arjun Shah Published: 2026-10-10T07:34:08.909Z Updated: 2026-10-10T07:34:08.909Z Event date: 2026-10-09 Section: Cloud ## General availability in the desktop app AWS announced brand-template support for Amazon Quick on October 9, 2026, and said brand assets were generally available that day in the Amazon Quick desktop app. The feature is designed to give teams shared visual standards for presentations and documents. [AWS announcement](https://aws.amazon.com/about-aws/whats-new/2026/10/amazon-quick-brand-templates-on-brand-presentations-documents/) ## From template files to published rules According to AWS, brand managers can upload PowerPoint or Word templates, or import them from a connected file store such as SharePoint. Quick extracts colors, fonts, logos, layouts and brand rules. A manager reviews and edits the extracted information before publishing the template to the organization. AWS says Quick selects a template for each task using guidance written by the brand manager, although users can choose another. It also says Quick follows template rules when creating assets: if a request conflicts with a rule, Quick explains the conflict and suggests an on-brand alternative. Administrators use custom permissions to control who can create and publish templates. [AWS feature details](https://aws.amazon.com/about-aws/whats-new/2026/10/amazon-quick-brand-templates-on-brand-presentations-documents/) ## Shared templates make validation more consequential The operational implication is a shift from finding the right template for each task to maintaining shared configuration. That could reduce repetitive setup, but it also gives the extraction-review step more weight: an incorrectly extracted rule could influence later output from a published template. Teams evaluating the feature should distinguish visual-policy controls from broader document governance. Publishing permissions and brand-rule handling should not be treated as guarantees of factual accuracy or regulatory compliance. A useful acceptance check would compare generated slides and documents against approved examples, including requests that deliberately conflict with template rules. This would test both ordinary formatting and the conflict-handling behavior AWS describes, rather than treating a published template as proof that every resulting asset is correct. ## Source references -