What would you like?
Generated presentations (PPTX) should respect the organization's configured corporate identity — brand color, accent color, logo, and fonts — instead of producing generically styled decks.
The platform can already generate presentations from a prompt, a website, or an uploaded document: the default assistant agent binds the pptx skill ("skillBindings": ["pptx"]) and runs it in the sandbox via run_code/file_write, then saves the deck to the documents hub. What's missing is making that output match the org's brand.
Why do you need this?
Decks produced for external/internal use are expected to be on-brand. Today the org branding config exists but has no effect on generated presentations, so every deck looks generic and has to be re-styled by hand.
Current state
- ✅ Presentation generation works (prompt / website / document → PPTX) via the
assistant agent + bundled pptx skill in the sandbox.
- ✅ Org branding is configurable —
appName, textLogo, brandColor, accentColor, logo/favicon assets (services/platform/lib/shared/schemas/branding.ts, stored per-org at {TALE_CONFIG_DIR}/<orgSlug>/branding/).
- ❌ The branding config is not passed into the pptx skill / generation context — output ignores brand colors, logo, and fonts.
Scope
- Feed the org's branding (brand/accent colors, logo image, fonts) into the pptx skill's generation context / template.
- Apply it as the default theme for generated decks, with the ability to override per request.
- Cover the prompt, website, and document generation paths.
Affected service
Platform (web app)
What would you like?
Generated presentations (PPTX) should respect the organization's configured corporate identity — brand color, accent color, logo, and fonts — instead of producing generically styled decks.
The platform can already generate presentations from a prompt, a website, or an uploaded document: the default
assistantagent binds thepptxskill ("skillBindings": ["pptx"]) and runs it in the sandbox viarun_code/file_write, then saves the deck to the documents hub. What's missing is making that output match the org's brand.Why do you need this?
Decks produced for external/internal use are expected to be on-brand. Today the org branding config exists but has no effect on generated presentations, so every deck looks generic and has to be re-styled by hand.
Current state
assistantagent + bundledpptxskill in the sandbox.appName,textLogo,brandColor,accentColor, logo/favicon assets (services/platform/lib/shared/schemas/branding.ts, stored per-org at{TALE_CONFIG_DIR}/<orgSlug>/branding/).Scope
Affected service
Platform (web app)