Skip to main content
A File Template is a document or presentation you upload once so Langdock can reuse its structure, layout, and styling whenever you generate similar files. Without a template, Langdock generates files from scratch using generic formatting. With a template attached, the new file matches your company’s format and brand out of the box.
Fill every slide type you want with realistic example content in its final formatting, keep fixed elements on the master, and name your shapes. See Building Presentation Templates for the recommended structure, good and bad example slides and a prompt to check your template with AI.
Presentations (.pptx, .ppt, .potx) and documents (.docx, .dotx, .pdf). Maximum file size is 200 MB per template.
Large language models cannot see the file visually while generating it. They write the underlying code (XML for PowerPoint, for example), then render and review. Small formatting mistakes on the first pass are normal. Langdock typically fixes them on the second pass, and you can always prompt it to correct specific issues directly.
It’s possible, but not recommended. A single generation covering many slides gives the model less room to focus on each one individually. Generate in chunks of 5 to 10 slides, lock each section in, then continue — you’ll get noticeably better results.
Yes. Open the template in the gallery and edit the instructions field. Sharper instructions are the best way to fix recurring issues (“always calculate subtotals from the line items”). The next time the template is used, the model follows the updated instructions automatically.
Yes. Templates share infrastructure with the Skills feature, so Skills must be enabled for the workspace. If Skills are disabled, templates won’t appear in the Library or in chat. On dedicated deployments, admins can also turn templates off while Skills stay enabled.
Anything that follows your template’s master layouts: title slides, chapter dividers, two-column comparisons, before/after layouts, and closing slides. Matching brand formatting, fonts, and colors from your template is also very reliable. Word documents, where the structure does most of the work, come out great with minimal iteration.
Complex data charts and tables, custom illustrations, timelines, process diagrams, and highly custom template masters with many layouts. Image placement often needs specific prompting to get right.
Ask for them specifically, slide by slide (“make this slide a timeline with four milestones”). A useful trick: ask the image generation tool to mock up the slide layout as an image first, then feed that image back and ask for the PowerPoint version. This gives the model a visual reference to translate into code.
All default roles include the Create skills permission, which lets users upload new templates. If an admin removes this permission under User management → Roles, the upload controls are hidden. By default, users can share templates with specific people or groups, while only admins can promote a template to the entire workspace.
Yes. When uploading a template, use the integration picker in the upload dialog to pull files directly from Google Drive, OneDrive, or another connected source instead of your local computer.
No. Templates and any files generated from them stay in your workspace and are never used to train AI models.
Knowledge bases are searchable document collections you can keep private or share, then reference in chat with @mention. Recent Files is your personal list of generated and imported files, so you can find them without digging through individual chats.
Not always. Files tied to a chat follow your workspace’s chat data retention policy: when a chat is deleted, its associated files are removed from Recent Files. Files not tied to a chat persist independently. Files stored inside a Folder are managed separately.
Yes. From any file in Recent Files, use Start chat with file in the context menu to open a new chat with that file attached.
There is no hard per-user limit on templates. Each template file must be under 200 MB. For very large or very custom master decks, we recommend splitting them into focused templates (for example, a sales deck template vs. a product update template) so the model can reason about them more effectively.