Skip to content

Templates

A template is a design your presentations wear: a palette per theme, the heading and body typefaces, the logos drawn on every slide, the predefined assets a deck may place (figures, screenshots, badges, partner / integration / customer logos), the layouts it may use, and a few sentences of guidance on how to compose in that brand. Agents find templates by name, kind, aspect ratio, tag and by the themes they support, so the same request produces on-brand output for everyone. The page lists, for each template, the themes it supports — Dark, Light or both.

A template has one of three kinds, chosen when it is created: Presentation dresses slide decks and pages, Report dresses executive reports, Video dresses the videos of the Video Studio (see Video templates). Whatever its kind, its assets are readable by any deck — there is no separate "asset pack" kind, the assets belong to the template whose brand they serve.

Templates live under Agent Studio > Templates in the sidebar. The page opens with the three steps of using one; they are spelled out below.

Use a template

1. Design it. A template declares the themes it supports — Dark, Light or both — with two switches, when it is created and at any time on the Configuration tab (Themes this template supports); at least one stays on. Each supported theme gets its own palette: the base palette carries the full set of colours and the typefaces and is read as Dark or Light from its background colour, and the other supported theme gets a variant palette in which only the colours you set differ — the accent, fonts and logos carry over. A template that supports a single theme limits every deck wearing it to that theme; switching a theme off removes the choice from those decks (a deck already in that theme is snapped to a supported one at its next save, and the note says so). The template's Preview renders a sample deck in each supported theme so the palettes can be judged before any deck exists.

2. Choose it when you create a presentation. New presentation, on the Presentations page or on a template's own page (New presentation with this template), asks which template the deck starts in and which of its supported themes to use, then opens the chat with the request written for you. In a chat, when you can see several templates, the template is your choice, never the assistant's: an assistant asked for a presentation without a template named lists your templates and asks which one to use before creating anything (it may recommend one, but a new deck is never created in a template you did not pick); name it ("in the Sales template") and it does not ask, ask for "no template" and the deck is drawn in the plain built-in look. Automations, and chats where the assistant cannot ask, use the platform's default presentation template — the built-in brand deck (the XTM One Brand Deck on an XTM One platform, the Filigran Brand Deck on Filigran Copilot) unless an administrator chose another company template in Settings > Parameters.

3. Change it anytime. A deck stays linked to its template rather than copying it: the palette, fonts and logos are read from the template every time the deck is drawn, so editing the template restyles every deck wearing it, at once. The deck's own Design section (Edit slides in the viewer) applies another template, or none, with a live preview, and offers the Dark / Light theme among the ones the chosen template supports. The slides, their words, the images uploaded to the deck and the theme it picked belong to the deck; deleting a template leaves its decks intact, in the plain look.

A template can also fix the deck defaults of new decks made from it, so nobody has to ask for the brand look each time — the theme (a default theme the template does not support is snapped to one it does), the 16:9 or 4:3 aspect ratio, the slide transition, and the covers: the hero backdrop, its colour and the theme of the title and closing slides, so a brand deck opens and closes on a dark gradient cover whatever the body's theme (the Filigran Brand Deck and the XTM One Brand Deck do: their decks open and close on their gradient cover). Every deck offers the Plain, Gradient, Split and Spotlight covers; the tiled ones — Mosaic, Cascade, Horizon and Pillar — are a brand's own artwork, offered only by a template that lists them under heroes in its Extra metadata ("heroes": ["mosaic", "cascade", "horizon", "pillar"], as the THREAD Conference Deck does). A cover default must be one of the covers the template offers. Deck defaults live in the template's Extra metadata and in the Design editor, and they dress new decks only — an existing deck is never restyled by them. A template can define the header and footer every deck wearing it fills once, and it carries the agent guidance every assistant reads before composing a deck in that brand: which slide opens, where the numbers go, how sparingly to use the accent color. The logo_mark asset — the symbol without the wordmark — is what the gradient cover draws as a faint watermark in its corner.

A template also decides how long a deck may run. A deck holds up to 100 slides unless its template says otherwise: max_slides in the template's Extra metadata raises the limit for the kind of deck the template is for — a board pack or a quarterly review that gives every dense dashboard its own slide outgrows a pitch deck's budget — up to 300, the platform's ceiling. The Filigran Brand Deck ships with 150; the XTM One Brand Deck keeps the default. The limit applies when a deck grows: the assistant's insert_slide and the editor's Add slide and Duplicate stop at it and say which limit it is, a deck without a template keeps the default, and a deck that is already longer than its template now allows (the template was changed, or the deck was moved to a shorter one) stays editable as it is — it simply cannot take more slides until it is back under the limit. Exports and the viewer handle a long deck like any other.

Only the template's palette, fonts, logos and footer pattern reach a deck. A template can restyle a presentation, but it can never inject arbitrary styling or scripts into the pages that render it.

The line at the bottom of every slide of a deck is not written on the slides — it is drawn from a few deck settings. A template decides what that line says for every deck wearing it, as a pattern with placeholders:

{{event}} - {{title}} - {{classification}}
  • {{title}}, {{subtitle}} and {{event}} are always available: the deck's title, the subtitle of its opening slide (as plain text — inline emphasis such as [[accent:...]] is not drawn in a footer) and the event the deck names. They need no declaration.
  • Every other placeholder is a variable the template declares — a key (classification), the label the deck's settings show (Classification), an optional hint and an optional default. A deck fills its variables once, in its Header & footer settings; until it does, a variable reads the template's default, or nothing when the template declares none.
  • An empty placeholder disappears with its separator: a deck with no event reads Quarterly review - Confidential, not - Quarterly review - Confidential. Everything that is not a placeholder is drawn as written.
  • A header pattern is optional and follows the same rules; it is drawn along the top of the same slides as the footer, and hides with it.

The XTM One Brand Deck defines {{event}} - {{title}} - {{classification}}. The event and the classification are both optional and have no default, so a new deck reads its own title on every slide, and "mark it Confidential" is one field, not a slide-by-slide edit.

On the Configuration tab, the Design editor's Header & footer card holds the footer pattern, the optional header pattern and the variables (up to eight), and previews the line with sample values as you type. The declaration is checked before it is saved — a placeholder no variable declares, a variable no pattern uses, a key that is not a lowercase word, a missing label — and a declaration with a problem is refused rather than drawn literally on every slide. Overview shows the pattern and the variables of a template that has them. A template with no pattern leaves the footer to each deck, which writes an event and a free footer text in the same settings. Changing the pattern restyles every deck wearing the template, like the palette; a field a deck set for a former pattern is kept, and the deck's settings say when no footer reads it.

The pattern is part of the design an assistant authoring a template can set (chrome in the template's metadata, with footer, header and variables), and get_template shows it to any assistant composing a deck, which is how "set the event to FIC 2026" reaches the right field.

Brand watermark

The same card has a Brand watermark switch. On, every content, agenda, roadmap, takeaways and dashboard slide of a deck wearing the template carries the template's mark (its logo_mark asset) faint in the top-right corner, over a soft glow of the brand gradient rising from the bottom corners — the cover's watermark, quietened for slides that have work to show. Title, section and closing slides keep their own backdrops. The mark is inked for the slide's theme, so it reads on a light slide as well as on a dark one. A template with no logo_mark asset draws nothing, and a deck that hides its logo hides the watermark with it. In the PowerPoint export the watermark is one picture under each body slide, behind blocks that all stay editable. An assistant sets it with "watermark": true in the template's chrome. The Filigran Brand Deck has it on.

Corner emblem

The Corner emblem switch, next to it, draws the template's mark small and in full colour in the top-right corner of every slide except the title and closing ones, which keep their cover. Unlike the watermark it also appears on section slides, so the brand sign stays in view through the whole talk. A template with no logo_mark asset draws nothing, and a deck that hides its logo hides the emblem with it. In the PowerPoint export the emblem is a picture of its own, like the logo. An assistant sets it with "emblem": true in the template's chrome. The THREAD Conference Deck has it on.

The built-in brand deck

Every platform ships the XTM One Brand Deck, a company-managed template: the product's own purple palette on dark surfaces (it supports the Dark theme only), Geologica and IBM Plex typefaces, six ordered colours for the series of a chart, four brand colours (the XTM One, OpenCTI, OpenAEV and OpenCRQ product colours, which the boxes of an architecture diagram can wear), the XTM One logo and mark, and the product material of the XTM platform as predefined assets: the OpenCTI, OpenAEV, OpenCRQ, XTM Hub, XTM One and XTM Platform logos and marks, the XTM platform architecture and product-flow diagrams, and product screenshots. It is the working example of a template every platform has, and the default presentation template of an XTM One platform; Filigran Copilot, Filigran's internal edition, also ships the Filigran Brand Deck and defaults to it.

Filigran Copilot also ships the THREAD Conference Deck, for the keynotes of THREAD, Filigran's conference: the colours of the THREAD design kit's color set on near-black slides (Cyan for highlights, the Lime-to-Blue gradient), and a Light theme drawn in the same set on Alabaster (the logo in dark ink, Cobalt Blue for highlights and the gradient's start, the mosaic tiles in their own colours); Elms Sans headings; title and closing slides on the Cascade cover of the THREAD marketing kit (the logo large in the top-left corner, tiles stepping down from the top-right one, the headline low over a thin rule and the speakers and date row), with Mosaic, Horizon and Pillar one click away in the slide's Selection tab - these four tiled covers are THREAD's own, offered by no other template; the "thread, powered by Filigran" logo in the corner and the mosaic "t" as the corner emblem. Its footer signs every slide with the edition, the talk's title and its classification (THREAD 2026 - The Road Ahead - Public): the edition reads THREAD 2026 until a deck sets another, and the classification is one field of the deck's Header & footer settings. It carries the same Filigran product, partner, integration and customer logos as the Filigran Brand Deck, plus the THREAD mosaic artworks, and its assistant guidance is written for a keynote: the session type above the title, every speaker and the date and room on the cover, numbered section dividers, few blocks per slide, and a closing slide with the speaker's contacts.

The logo is drawn automatically on every slide of a deck made from it. To give an assistant your own figures to place — your architecture diagram, your screenshots, your partners' logos — duplicate it or create a template of your own and add them on its Assets tab.

Predefined assets

The assets of a template are what an assistant places when you ask for a figure, so it uses the actual one instead of drawing an approximation.

Every asset has a description that says what the figure shows and which surface (dark or light) it is drawn for; assistants read these descriptions to pick the right file, and you see them in the Assets tab. A template can hold hundreds of assets, so an assistant never reads the whole list: it asks the template for one role ("the partner logos") or one keyword and gets only what matches — ask for "a logo wall of our partners" and it lays the right logos out in a logo grid.

Upgrading an XTM One platform

Earlier versions also shipped the Filigran Brand Deck, Filigran's own house style, on XTM One platforms. It is reserved to Filigran's internal edition: on the first start after the upgrade — whether AI is switched on or off — it is removed together with every one of its assets and their stored files, and whatever the object store could not delete at that start is deleted within the hour once it answers again. The decks made from it keep their slides and are drawn in the plain look until you choose another template in their Design section, such as the XTM One Brand Deck. A picture a slide had placed from it is removed with it and nothing is drawn in its place; editing that slide, asking an assistant to rewrite the deck or restoring an earlier revision still works — the picture stays gone and the history says how many pictures were left empty — and you can put another picture in its place at any time. If an administrator had chosen it as the Default Presentation Template, the setting returns to the built-in default. A copy you made with Duplicate is your own template and stays: delete it from the Templates page if it should go too.

Upgrading from the asset libraries

Earlier versions shipped the partner, integration and customer logos as three separate asset-library templates next to the brand deck. On an XTM One platform the first start after the upgrade removes them, logos included. On Filigran Copilot, which ships the Filigran Brand Deck, it moves their logos into that deck instead — the same files under the same identifiers, so every slide that already placed one keeps it — and removes the three emptied libraries. A template of that former kind you created yourself keeps working with its assets, but no new one can be created: give the logos to a Presentation template instead. Import refuses a package of that kind and names it, so edit the kind in the export first; Duplicate copies such a template as a Presentation one, keeping the palette keys and layouts a presentation honours; whatever it had to leave out is listed in the audit log entry of the copy.

Built-in templates carry a Built-in badge and are read-only: they are kept in sync with the platform on every startup, so an edit would be undone by the next upgrade. To derive your own palette from one, use Duplicate — the copy is yours to change.

Video templates

A Video template keeps every video that wears it to the same look. Its palette (per theme), fonts and logos work as they do for a deck - the logo and logo_light assets are drawn on the title and closing cards, the logo_mark asset is the watermark - and its rules live in extra_metadata.video:

  • aspect_ratios — the formats the brand ships, the first one the default (16:9, 9:16, 1:1, 4:5);
  • purposes — what the template is made for: product_demo, brand_film, event, launch, explainer, social (New video suggests it for those kinds of video);
  • defaults — what a video gets when it leaves it unset: theme (mode, background - aurora, gradient, mesh, grid, mosaic or solid - and watermark, the corner the mark is drawn in: a video writing none keeps none, and saving it says the template draws one), default_transition ({"type": "auto", "pace": "calm"} or "dynamic" to pick each cut from the scenes on either side, or one named type with an optional duration), captions, voiceover (enabled, voice, style, speed, and pronunciations: the brand's product names as the voice must say them), music (the brand's sound: a built-in track - bright-horizon, deep-focus, signal, ascent, late-notes, momentum or quiet-light - with its volume, ducking, duck_db, fade_in and fade_out; a video naming its own music keeps it, and "music": {"enabled": false} plays none);
  • scene_defaults and overlay_defaults — the same per scene type (title, statement, recording, slide, clip, image, outro: the card style, how a statement is revealed and aligned and how dark its backdrop is, the browser window, the cursor, the camera) and per overlay type (style, position, duration, and a picture overlay's width and opacity). What a scene shows - its text, its lines, its recording, its backdrop, its narration - is never a template's to preset, with one exception: a scene type's defaults may add the brand's marks as picture overlays by their role, never a file - "clip": {"overlays": [{"type": "image", "asset": "logo_mark", "position": "top_right", "width": 0.06, "duration": 60}]} puts the template's mark on every AI shot and video clip, before the scene's own overlays, unless the scene draws that mark itself;
  • intro and outro — {"required": true, "scene": {...}}: the title card added before the first scene and the closing card added after the last when the video has none ({title} in a text is the video's title); with required: false the card only lends its look to one the video writes;
  • locked — the paths whose template value always wins, such as theme.background, captions.style or scenes.recording.frame, plus theme.palette, which keeps the template's colours and logo over any the video names;
  • shots — the art direction of every AI shot made for a video wearing the template (see AI shots wear the template's art direction): style, the look added to the prompt of a shot drawn from a description (up to 600 characters: the light, the lens, the materials, the palette in words, the motion); avoid, what no shot shows, one term each (up to 16: added to the negative prompt of a video model that takes one, and read on the finished shot's frames, which says when it shows one - name visual things, never text or a logo, which a shot made from a real screenshot carries). For example "shots": {"style": "Photographic, natural light, deep navy and cyan tones.", "avoid": ["laser beams", "starfields", "holograms"]}. It steers the shots, never limits how many a video has.

Every preset must make a valid video and every lock must name a preset: a rule that does not is refused when the template is saved, with the field named. The Overview tab shows the rules (Video rules), and New video with this template starts a video in it. Video templates ship with the platform for every kind of video: Filigran Product Video, Filigran Brand Film, Filigran Event Loop and THREAD Conference Video on Filigran Copilot, XTM One Product Video, XTM One Brand Film, Threat Briefing and Social Teaser on every platform (see Video Studio templates). Every built-in video template carries the assets of its brand's deck: the four Filigran ones the whole library of the Filigran Brand Deck (product screenshots, diagrams, badges, team and event photos, and the product, partner, integration and customer logos), the THREAD one that of the THREAD Conference Deck, and the XTM One ones the product logos, diagrams and screenshots of the XTM One Brand Deck. The assistant places them as image scenes or statement backdrops, draws a screenshot onto a screen in a picture, or animates them as a figure - a wall of customer logos, an architecture whose boxes wear the product marks. The first product video a platform ships is the default of a video an assistant creates without naming a template, and freestyle: true opts a video out of any template (New video starts in free style unless a template is chosen or suggested for the kind of video).

Create a template

From Templates, Add Template opens the creation form: a name, a description, the kind (Presentation for slide decks and pages, Report for executive reports, Video for Video Studio videos), the aspect ratio, tags, and — for administrators — whether the template is company-managed. A Presentation template also declares the themes it supports with two switches, Dark and Light — both on by default, at least one stays on. Generate with AI drafts the palette from a brief (see below) and proposes the themes its palettes read as, which you can still change; Preview renders a sample deck in it before you save.

Once the template exists, its detail page has three tabs:

  • Overview — the description, the Design (the palette per theme, marked Supported or Not supported), the attributes agents search by (kind, aspect ratio, tags), the layout catalog, and how many times agents retrieved the template
  • Configuration — the editable fields, the Design editor (Themes this template supports, one palette per supported theme with its colours — the base palette comes first and also carries the fonts — and the deck defaults), the layouts and the sharing settings; the raw JSON stays available under Advanced (JSON). Every palette shows its chart series (chart_1 to chart_6, drawn as a small bar preview that follows each keystroke; each theme tunes its own, and an empty series keeps the built-in colour, chart_1 the accent) and its optional brand hues (brand_1 to brand_4, the product colours an architecture node or zone can wear; an empty one falls back to the chart series of the same rank, and a variant palette inherits the base palette's). An empty field shows, dashed, the colour a deck draws instead: the colour it falls back to, or what a variant palette inherits from the base palette - its accent, gradient and brand hues, and every colour when the base palette's background is not set. When Advanced (JSON) also holds a variant for the base palette's own theme, which decks in that theme lay over the base, the form names the keys it sets, and editing one of them in the base palette removes it from that variant - except background, which decides the base palette's theme: remove a variant's background in Advanced (JSON). Preview the unsaved design opens the template preview on everything being edited - the name, the aspect ratio, the layouts, the palettes and the deck defaults - so it shows what saving would produce; a name, an aspect ratio or layouts the save would refuse (a blank or over-long name, an over-long aspect ratio, layouts JSON that does not parse) are previewed as saved, and a palette value the save would refuse is left out of the preview.
  • Assets — the files bound to the template

The old theme label

Templates created before this version could carry a free-text theme label (dark, corporate, …). It never changed a deck's colours — only the palettes do — and is no longer part of the design. Where one is still set, Configuration shows it as Search label (legacy) with a Clear action; older agent instructions that looked templates up by that word keep working until it is cleared.

Templates are shared like every other resource: private to you, shared with groups, or company-managed for everyone. The Export action downloads the whole template as a package (metadata plus assets) that Import on the Templates page recreates on another platform.

Generate a template with AI

Rather than typing color values by hand, let the assistant draft the template. Generate with AI is available on the Templates page, on the creation form, and on the Configuration tab of an existing template.

  1. Write a design brief in plain language: the audience, the mood, two or three colors — "a light corporate deck for quarterly reviews, navy and gold, understated".
  2. Add palette hints if you have them: a hex value or a color word, one chip each.
  3. If the template already holds an image asset, pick it under Sample colours from a logo: the dominant colors of the image are handed to the assistant so the palette sits naturally around your logo.
  4. Click Generate. A live preview of a sample deck in the proposed palette appears next to the result, together with the name, labels, layout catalog and agent guidance the assistant drafted, and the colors it read from the logo.
  5. Refine in follow-up rounds — Refine this result with "warmer accent" or "swap the heading font for a geometric sans" — or Regenerate from the brief to start over.
  6. Apply to form fills the fields. Nothing is saved until you save the template, and every field stays editable.

When you generate from the Configuration tab, Start from the current configuration keeps whatever the brief does not mention; turn it off for a fresh design. The proposal is checked against what the renderer supports: a value it would ignore is listed as an adjustment rather than silently dropped.

A logo first

To build a template around a logo, create the template, upload the logo on the Assets tab with the role logo (and the dark-on-light variant as logo_light), then run Generate with AI from Configuration with the logo selected. The logo is then drawn on every slide of the decks made from the template, and the palette is sampled from it.

Assets

The Assets tab holds the files a template brings to a deck. Each asset has a role that tells the renderer and the agents what it is: logo, logo_light, logo_mark, product_logo, partner_logo, integration_logo, customer_logo, people_photo, background, illustration, diagram, screenshot, badge, icon, image, font, or other — and a free-text description that says what the file shows. A template holds up to 400 assets; the tab filters them by role (each role with its count) and by a keyword in the name or the description — the same two handles an assistant uses.

  • The logo asset (and logo_light on the light theme) is drawn by the deck chrome on every slide.
  • Other images are placed by the assistant when you ask for them — a product logo on the title slide, a background on a section divider, a diagram in an image block, several logos at once in a logo grid.
  • The description is what an assistant picks an asset by ("the architecture diagram", "the dark-surface variant"), so write it for a reader who cannot see the file: what it shows, and whether it is drawn for a dark or a light surface.

You can add, relabel, replace and remove assets independently of the rest of the template. Replacing a file keeps its identity, so decks that already reference it pick up the new version. SVG files are cleaned on upload: scripts and remote references are removed before the file is stored.

Ask an agent to author a template

The built-in Template Designer agent creates and refines templates from a conversation: describe the brand, answer its questions, and it creates the template, attaches the logos you uploaded to the chat, writes the deck defaults and the guidance, and generates a preview deck for you to judge. It cannot read colors out of an image — for that, use Generate with AI in the UI and bring the result back to the agent to refine.

Next step

Generate a deck in your new brand: see Presentations.