Help & knowledge base
Find your answer.
Step-by-step guides for getting Templ8r live in your tenant, writing tokens, managing plans, and fixing the things that occasionally break.
Categories
↗Getting started3 articles
Install the solution, grant access, generate your first doc.
≡Templates & tokens1 article
Add tokens to your branded Word file, bind them to D365, fix unbound ones.
✶Generation & timeline0 articles
Where docs land, async vs sync, Word vs PDF, bulk runs.
£Billing & plans1 article
Tier comparison, what counts as a doc, switching plan, invoices.
◇Security & data1 article
What we read, where it's stored, ephemeral mode, deletion.
⚙Troubleshooting2 articles
Modal won't open, tokens render literally, generation 502.
Recently updated
- Getting startedInstall the Templ8r solution in your D365 environmentDownload the managed solution, import it via Solutions in Power Apps, publish. Adds the ribbon button + 6 web resources to your tenant. ~10 minutes.
- Getting startedGrant admin-consent + provision the Application UserTempl8r is a multi-tenant Entra app. A Global Admin grants consent once. Then a System Admin runs /onboard/auto to create our Application User in Dataverse.
- Getting startedGenerate your first document — ribbon click walk-throughOpen a record, click the Templ8r ribbon button, pick a template, click Generate. Word + PDF land on the Timeline in 1–3 seconds.
- Templates & tokensHow tokens work — basics, lookups, multi-hop, format hintsTokens are {{column}} placeholders in your branded Word file. Templ8r reads bound Dataverse fields at generate-time and splices values back in. Supports lookups, multi-hop chains, repeating rows, format hints, and conditionals.
Couldn’t find it?
Email a human.
We reply within one business day. support@templ8r.co.uk