Skip to main content
Idea

Apply an org-wide theme to existing documents

Related products:Lucidspark
  • May 19, 2026
  • 1 reply
  • 22 views

Forum|alt.badge.img

Summary: Please add an organization-level Theme/Brand Kit that can be defined once and applied to any new or existing Lucid document.

Problem: We maintain brand standards (fonts, color palette, line/connector styles, title block/page layout, and a logo). Today, themes are per-document and templates help only for new docs—updating existing documents (such as AI generated documents that are uploaded to Lucid) requires manual work (copy/paste, format painter, re-theming page by page).

Request / Requirements:

  • Create an org-level Theme/Brand Kit with:
    • Fonts (heading/body styles)
    • Color palette + semantic tokens (Primary/Secondary/Accent/etc.)
    • Default shape + connector styles
    • Page header/footer/title block components + logo
  • “Apply Theme” action for existing docs with options:
    • Whole doc vs selected pages
    • Update only theme-linked objects vs override manual styling
    • Style/color mapping from old → new tokens
  • Set default for new documents
  • Admin governance, versioning, and optional push updates to documents

Value: Faster creation, consistent branding across teams, easier rebranding updates, fewer manual formatting errors.

May 22, 2026

Hi ​@ggoodman, thanks for this idea! We encourage anyone else who’s interested in this to upvote this post and share any additional details about your use case or what you’d like to see in this experience. For more information about how we manage feedback in this community, please take a look at this post:

As a workaround, I recommend using our Custom Shape Library functionality, as these can be shared across users within an organisation similarly to templates that you have mentioned, and help to use branded components across all documents.

Cheers!

Comments

Zuzia S
Forum|alt.badge.img+8
  • Lucid community team
  • May 22, 2026

Hi ​@ggoodman, thanks for this idea! We encourage anyone else who’s interested in this to upvote this post and share any additional details about your use case or what you’d like to see in this experience. For more information about how we manage feedback in this community, please take a look at this post:

As a workaround, I recommend using our Custom Shape Library functionality, as these can be shared across users within an organisation similarly to templates that you have mentioned, and help to use branded components across all documents.

Cheers!