Changes an email template: any of name, description, format, align, subject, body and tags; a field left out stays as it is, description: null clears it, and tags replaces the whole tag list. The same checks as creating apply to the result (known tags, {{link.url}} present, no scripts in HTML, images only from this workspace's uploads); a tags list that declares a link-like custom tag is refused with details.code custom_tag_is_link, and a template whose tags are not sent keeps the ones it has. Tags are written {{entity.field}}, or {{entity.field|fallback}} for text used when the value is empty. Built-in tags, filled by LinkDrop for each recipient: contact.firstName: The first word of the contact's name. (e.g. Ken); contact.name: The contact's name: the name the team gave them, else the name they gave. (e.g. Ken Lee); contact.lastName: Everything after the first word of the contact's name. (e.g. Lee); contact.email: The contact's email address. (e.g. ken@example.com); contact.company: The domain of the contact's address; empty for a webmail address such as gmail.com. (e.g. acme.com); contact.note: The team's note on the contact, as written; it goes into the email exactly as it is. (e.g. Met at the October demo day.); contact.tags: The contact's tags, comma-separated. (e.g. Investor, Seed); contact.firstSeen: When LinkDrop first saw the contact, e.g. October 22, 2026. (e.g. October 22, 2026); contact.lastSeen: When the contact was last seen, e.g. October 22, 2026. (e.g. October 22, 2026); contact.visits: How many times the contact has viewed, as a number. (e.g. 3); link.url: The recipient's own LinkDrop link to the document or project; one link per person, reused on every render. (e.g. https://lnkdrp.com/s/example); link.password: The password of the recipient's own link; empty when the link has none. Filled when the email is sent and for a member signed in to the app; a connected agent sees [password]. (e.g. chris58); document.title: The document's title (document emails only). (e.g. Q3 investor update); project.name: The project's name (project emails only). (e.g. Series A data room); sender.name: The name of the member the email is from. (e.g. Chris); sender.firstName: The first word of the sender's name. (e.g. Chris); sender.email: The sender's LinkDrop account email (not necessarily the Gmail address the email goes out from). (e.g. chris@example.com); workspace.name: The workspace's name. (e.g. LinkDrop). {{link.url}} is one link per recipient: their own LinkDrop link to the one document or project the email is rendered for, reused on every render. A template's links (its own documents and projects) put several in one email, each wherever its {{link.}} is written: every recipient gets their own tracked link to each. A project is the other way: one link to all of its documents. {{link.url}} appears in every template without links; a template with links places at least one of them. Custom tags are {{custom.name}}, each declared in tags with a description of what it stands for, and hold words taken from lnkdrp_render_email's values; a custom tag whose name or description reads as a link (..._link, ..._url, an address) is refused as validation with details.code custom_tag_is_link. An HTML body shows images only from this workspace's uploads: an image is uploaded with lnkdrp_upload_email_asset and placed with the imgTag it returns (lnkdrp_list_email_assets lists those already uploaded). Any other image source (another site, data:) is refused as validation with details.code image_not_an_asset, on save, render and send; a javascript: URL or a is details.code html_not_allowed. The text version shows an image as [alt]. Each image is kept under 10 MB on every plan (big images make emails slow to open and more likely to be clipped or land in spam): an uploaded image over it in the body is swapped for a smaller copy on save. One email shows at most 10 images, 20 MB in all: over that, the save makes the images smaller, the largest first, until the email fits (reason email). imagesResized [{ name, from, to, assetId, note, reason }] lists each one. When it cannot fit, the save is refused as validation with details.code too_many_images or images_too_heavy, a sentence saying the limit and what to change, and details.limits. Emails already rendered from it keep the text they were rendered with. Each change that changes something is saved as the template's next version (template.version); lnkdrp_list_email_template_versions lists them. A template saved by someone else after this connection last read or saved it (or after baseVersion or baseUpdatedAt) is not overwritten: the call answers validation with details.code conflict, currentVersion and currentUpdatedAt, and nothing is saved. Returns the template, unusedTags and warnings: notes as { code, message } on a template that saved as sent. body_self_centred: the html body's outermost element centres itself with auto side margins (margin: 0 auto) while align is left, so the email still shows centred; the body is saved unchanged. link_unused: one of the template's links is not placed in the body, so that document goes out to no one. no_documents: the template has no links of its own, so each drop or email made from it takes its document from its own docId or projectId. visibility makes the template private to its owner or shares it with the team (not a document's visibility, lnkdrp_set_doc_visibility); it is sent with no other field (visibility with another field is validation) and moves no version. Making it private takes its owner or a workspace owner or admin, and an owner or admin making someone else's template private makes it private to that person; sharing a private template takes its owner; anyone else is forbidden. Another person's private template is not_found. projectIds files the template under projects: it is sent with no other field (projectIds with another field is validation), replaces the projects this person can see, moves no version and is not saved as a draft, so any member files a template whether or not they may publish it. Only the template's publishers change it live (its owner, workspace owners and admins, its chosen publishers, or everyone when it is set so). Anyone else's change is saved as their own draft, one per person, and the live template is unchanged: the result has saved: draft, draft { id, version, baseVersion, updatedAt, reviewUrl, publishers } and message; a publisher saves a draft with draft: true. The next update by the same person changes the same draft. On Free a non-publisher is forbidden with details.code publisher_required and upgradeUrl. lnkdrp_publish_email_template_draft publishes a draft.