Company Templates for Document Generation Skills

Overview

The pptx, docx, and pdf skills build documents from your organization's own templates. The output inherits the fonts, colors, layouts, logos, and footers of the template file it was built from. Templates are stored in one fixed Knowledge Base folder called templates-conduct. Creating and maintaining that folder is the only configuration involved.

Before the agent plans a document, it lists the templates it can see in that folder and asks the user to confirm one. If the folder does not exist, or holds nothing the user has access to, the document is built without a template and the agent says so in its reply. A user can manually attach templates in the chat, but note that these will not be added automatically to the templates folder.

Who is it for?

Administrators responsible for the Knowledge Base of a company using Unique AI Conduct. End users need no setup: they ask for a document and confirm a template when prompted.

If you're unable to access the features discussed on this page, it's possible that your company does not have access or hasn't upgraded to the latest version yet. Please reach out to your internal support team or Unique's customer success team for assistance.

Where Templates Live

Templates are read from a folder named templates-conduct at the top level of the Knowledge Base. The name is fixed, and a folder with any other name is not read.

Two locations inside it are read:

1. Directly in templates-conduct

2. In one of its immediate subfolders, for example templates-conduct/Investor Relations/

Both are read on every request, and you can use either or both. Folders nested more than one level below templates-conduct are not read. In general we encourage using subfolders to keep things organized. The subfolders also simplify access management.

templates-conduct/
├── Corporate Master.pptx
├── Letterhead.docx
│
├── Investor Relations/          [read: IR team]
│   ├── Pitch Deck.pptx
│   └── Fact Sheet.pdf
│
└── Credit/                      [read: credit desk]
    └── Credit Memo.docx

There is no separate folder per file type. The file extension is the filter, so one subfolder can hold .pptx decks, .docx templates and .pdfs together.

Setting Up the Folder

Step 1: Create the folder

In the Knowledge Base, create a folder named exactly templates-conduct at the top level. Check the spelling: a misnamed folder is indistinguishable from a missing one. Once the folder has been created it is recommended to turn off ingestion of the folder by clicking Configure File Ingestion and setting Ingestion Type to Skip Ingestion.

Step 2: Upload the template files

Upload your .pptx, .docx, and .pdf templates, either directly into the folder or into subfolders one level down.

Upload real working files. The agent builds a deck by duplicating slides from the template, and a document by editing a copy of it, so the file has to contain the actual layouts. A style guide describing them cannot be used for this.

Step 3: Grant read access

Access is granted per folder, as with any Knowledge Base content, and listings are filtered per user. A user who cannot read a subfolder does not see its templates, and the subfolder itself is invisible to them. Access must also be granted to the templates-conduct folder. Normally the whole company should be able to access the templates-conduct folder, while subfolders can be restricted to specific groups or persons.

Step 4: Check the folder is in scope for the space

If a Conduct space limits its Knowledge Base access to selected folders, templates-conduct has to be among them. A folder outside a space's scope behaves, for that space, as if it did not exist.

Step 5: Verify

Open a Conduct space as a user and ask for a document, for example "create a short presentation about our Q3 results". The confirmation dialog should list the templates you expect that user to see.

What Users See

1. A user asks for a document to be created in a Conduct space.

2. The agent lists the templates of the matching type and opens a single confirmation dialog. Each entry is the template's path relative to the templates folder: Corporate Master.pptx for a file directly in it, Investor Relations/Pitch Deck.pptx for one in a subfolder. If the user has uploaded a template in the current chat it will also be listed.

3. One entry is pre-selected. If the user named a template in the conversation, that one is proposed. Otherwise the agent falls back to the most reasonable match by filename, a generic master, or the most recently modified file.

4. Two further entries are offered: uploading a template to the chat instead, and building without a template.

5. The agent builds the document from the confirmed template and delivers it as a download at the end of the turn.

Confirmation happens on every request. There is no saved default that skips the dialog, and nothing is carried over from an earlier session.

The dialog lists everything the agent can see in the supported locations, so it has no search field: running the listing again returns the same set. When none of the listed templates is right, a user can attach their own file to the chat, or name a specific Knowledge Base folder in the conversation, and the agent will attempt to list that folder instead. Neither of those needs an admin.

A file a user attaches to the chat is used for that conversation only. It is never written into templates-conduct.

Separating Templates by Team

Subfolders are the mechanism for this. Give each team a subfolder and grant read access accordingly: the credit desk sees Credit/, the IR team sees Investor Relations/, and templates in templates-conduct itself are available to everyone who can read it.

Because listings are access-filtered, this also keeps each team's confirmation dialog short. A user sees only the templates they have access to.

Keeping the Folder Current

Two practical points:

• Curate the folder. Every template a user can read appears in their confirmation dialog. A folder holding the current set is easier to choose from than one holding every past variant.

• Name templates descriptively. Corporate Pitch 2026.pptx or QBR Template.pptx rather than final_v3.pptx. The filename is what the user reads in the dialog and what the pre-selection is matched against.

Template Quality

The agent stays close to the template. For a presentation it duplicates real slides, and for a Word document it edits a copy, so whatever is in the file is reproduced in the output. The template largely determines the quality of what comes out.

• Keep the file clean. Stray text boxes, off-slide elements, orphaned placeholders, and inconsistent footers are copied along with everything else.

• Include everything you expect in the output. If a layout, footer, or branding element is not in the file, the agent has nothing to copy it from.

• For presentations, include a cover slide, a closing slide, and a range of content layouts (title with bullets, two columns, image with text) so there is a suitable slide to duplicate for each part of a deck.

• Keep placeholder text realistic in length. The agent matches its content volume to what the template slide originally held.

• Colors, fonts, and master backgrounds come from the template file. If output looks off-brand, the template file is the first place to look.

When No Template Is Available

If the templates-conduct folder has not been created, is empty, or if the user does have access to any template, the agent will create the document from scratch. The agent adds one line to its reply explaining why no template was used. The two causes need different fixes:

Which Skills Use the Templates Folder

FAQs

Q: Does the folder have to be called templates-conduct?
A: Yes. The name and the location are fixed, and no other folder is read by default. A user can point the agent at a different folder within a conversation, but that applies to that conversation only.

Q: Do templates need to be ingested?
A: No. Templates are found by listing the folder, so whether a file has been ingested makes no difference to discovery.

Q: Can I set a default template so users aren't asked every time?
A: No. The confirmation dialog is shown on every request. The most likely template is pre-selected, so confirming it is a single step.

Q: Can templates sit deeper than one subfolder?
A: No. Only templates-conduct and its immediate subfolders are read. Templates nested deeper than that need to be moved up to one of those two levels.

Q: A user can't see a template that is in the folder.
A: Check their read access on the subfolder holding it. Listings are access-filtered, so a subfolder a user cannot read looks the same to them as one that does not exist. Then check that the space's Knowledge Base scope includes templates-conduct.

Q: How many templates can the folder hold?
A: There is no configured limit. Every template a user can read is listed in their dialog, and very large folders may not be listed in full, so keep the set curated.

Q: Can users bring their own template?
A: Yes. Attaching a file to the chat uses it for that conversation. Chat attachments are never saved into templates-conduct; company-wide templates are added by an admin.

Q: Users report that a document preview looks wrong although the file itself is fine.
A: The in-platform preview substitutes fonts and can shift spacing. Download the file and open it in PowerPoint or Word to see the actual layout.

Q: Is there anything to enable on the space?
A: No. The document skills are available in Conduct spaces without configuration and read templates-conduct whenever it exists.

Security

• Templates are Knowledge Base content and are subject to the same access controls as anything else stored there

• Template listings and downloads are filtered by the requesting user's own permissions. The agent cannot read a template the user could not open themselves

• Templates are read over the platform's internal APIs; no external network access is involved

• The agent never writes to templates-conduct. Generated documents and chat attachments are not saved there, so a one-off draft cannot become a company template by accident