# Shared email templates in Pipedrive: who can edit them, merge fields, and keeping the team library clean

https://salesbond.app/blog/pipedrive-shared-email-templates-team/
Published: 2026-10-04 · Updated: 2026-10-26

An email template in Pipedrive is either private or shared. Shared means everyone on the account can pick it and send it, but a regular user can only edit templates they created themselves; to change somebody else’s shared template you select it, edit the text and save the result as a new template ( [Pipedrive: email templates](https://support.pipedrive.com/en/article/email-templates), updated September 3, 2026). That one rule is why shared libraries fill up with near-copies. So a shared library needs two things the setting does not give you: one named owner per template, and a naming rule everyone follows. Below is how we set that up for a team of three to eight, what merge fields do when the data behind them is missing, and when to skip all of it and keep templates personal.

## Three versions of the same follow-up

An invented scene; the mechanism is Pipedrive’s.

A five-person team sells a linen-tracking app to independent hotels. Mara Linden, the senior rep, wrote the team’s first good template a year ago: a short recap after the first demo, with the hotel’s name and the next step filled in from the deal. She shared it, and everybody used it.

Then Joel Okafor joined. He liked the recap but wanted a line about the one-floor pilot, because every hotel manager asks about it. He opened Mara’s template, added the line and hit save. Pipedrive saved his edit as a new template under his name, “Demo follow-up v2”, and left Mara’s original exactly as it was.

A month later a teammate spotted a wrong product name in Mara’s template. As a regular user he couldn’t touch her original, so he did what Joel did: edit, save as new, call it “Demo follow-up (fixed)”. Now there are three, side by side in the picker. The newest rep picks the one at the top. It has the wrong product name.

Nobody broke anything; each person did the only thing the setting allows. The library simply has no owner, and like every unowned shared thing in a CRM it grows until people stop trusting it, the same pattern we described for fields and pipelines in [who owns CRM data in a small sales team](https://salesbond.app/blog/crm-data-ownership-small-sales-team/).

## Private or shared: what the setting changes in Pipedrive email templates

There are two ways to create a template, and both ask the same private-or-shared question. You can write an email in the composer and save the draft as a template, or go to Choose template > Manage templates and add a new one from scratch ( [Pipedrive: email templates](https://support.pipedrive.com/en/article/email-templates)).

The setting controls who can see and use the template, nothing more. Private shows up only in your own picker; shared shows up for everyone on the account.

What it doesn’t change is who may edit. Editing rights follow the author, not the visibility. Sharing your template doesn’t hand your teammates a pen; it hands them a copy machine. We tell every new rep that, because people expect “shared” to work like a shared document. Quote documents have the same ownership problem, plus fields that must match the deal: [quote template fields that match the CRM deal](https://salesbond.app/blog/quote-template-deal-fields-sales-team-crm/).

Most templates in a small team are born the first way, from a good email someone expects to write again. Fine. Just keep it private for two or three sends, see if the wording holds up, then share it under the naming rule below.

## Why editing someone else’s template makes a copy

Because that’s the only edit a regular user is allowed to make. The help article puts it in one sentence: regular users can only edit templates they created themselves, and to use a shared template made by someone else you select it, make your changes and save it as a new template ( [Pipedrive: email templates](https://support.pipedrive.com/en/article/email-templates)). It says nothing about admins, so we treat it as the rule for regular users and don’t build our process on whatever an admin might be able to do.

The rule protects the author’s text from quiet rewrites. The price is that every improvement by a non-author becomes a sibling.

![Diagram: regular users edit only their own templates; an edit to someone else's shared template is saved as a new copy.](https://salesbond.app/wp-content/uploads/2026/10/pipedrive-shared-email-templates-team-2.png)

Two consequences follow. The author is the only regular user who can fix the original, so while she’s on holiday the typo stays, or someone makes a corrected copy. And a copy carries no link back to its source: three months on, nobody can tell from the picker which “Demo follow-up” is current.

None of this is a bug to wait out. You design around it.

## A naming rule and one owner per template

Every shared template gets exactly one owner, and the owner is its author in Pipedrive, because that’s the only regular user who can edit it. Not “the team”, not “whoever uses it most”. When someone wants a change, they send it to the owner. The owner edits the original and the library stays at one copy.

When an owner leaves the company, thier templates become orphans. They still work, and no regular user can change them, so someone recreates each one under their own name and tells the team which version to use. Whether an admin can then delete the old one is not something the help article covers, so check it in your account before you count on it. Recreating an orphan is the one time a copy is the right move.

The naming rule exists so the picker reads like an index instead of a pile. Ours has three parts: what the email is for, when it’s sent, and who owns it. “Demo recap · after first demo · Mara.” “Proposal reminder · day 7 · Joel.” “Lost deal, door left open · at close · Mara.” The owner’s name at the end is not vanity. It tells a rep who to ask before they reach for the copy machine. Anything that doesn’t follow the pattern is, by agreement, a personal template someone shared by accident.

## Merge fields: what fills in, what leaves a hole

Merge fields pull data from the item the email is linked to: a deal, a lead, a project, a person or an organization. They work in the body, in the subject line and inside links ( [Pipedrive: email templates](https://support.pipedrive.com/en/article/email-templates)). The subject line is the one people forget: “Next steps for [organization name]” is a bad email when the field comes back empty. For the subject lines themselves, we cover [sales email subject lines by stage](https://salesbond.app/blog/sales-email-subject-lines-by-stage/) and how to change a shared template one variable at a time.

Two conditions have to hold for a field to fill in, and both are about the data, not the template:

- The email has to be linked to the right item. A deal field fills in only when the email is linked to an existing deal. If the contact has more than one deal, the help article says to send from that deal’s detail view or link the email in Sales Inbox.
- The field has to have a value. Pipedrive’s help says you’ll see a warning if a merge field is left empty ( [Pipedrive: email templates](https://support.pipedrive.com/en/article/email-templates) ), which is useful exactly as long as a person is looking at the screen.

One more limit from the same article: merge fields don’t work for labels or for fields created from contact sync, such as job title or birthday. Keep those out of shared templates altogether.

The second condition is why we treat templates and data hygiene as one subject. Templates can also be used in group emails and automated emails ( [Pipedrive: email templates](https://support.pipedrive.com/en/article/email-templates); we wrote separately about [how automated emails pick a sender](https://salesbond.app/blog/pipedrive-automated-email-sender/)). The help article doesn’t say what happens to an empty field in a group or automated send. Nobody is watching a composer there, so we plan as if the gap goes out to the buyer. If your recap uses a custom “Next step” field and your reps fill it in about half the time, you don’t have a template problem. You have a required-field problem wearing a template’s clothes, and the fix belongs with the data owner.

Our working rule: a shared template uses only fields the team has agreed are always filled at that stage. Deal title, person name and organization name are usually safe. A custom field is safe once a filter shows it’s populated on the deals that will get the email. If you can’t promise the field, write the sentence without it.

Which emails to automate, and in what order, is a separate decision; we walked through a post-demo sequence in [Pipedrive Sequences for deal follow-up](https://salesbond.app/blog/pipedrive-sequences-deal-follow-up/).

## A ten-minute monthly cleanup

Once a month, on the same day as the pipeline review, so it doesn’t get its own excuse to slip.

1. Open Choose template > Manage templates and read the shared templates from top to bottom. Pipedrive lets you reorder templates by dragging and delete them with the trash icon ( [Pipedrive: email templates](https://support.pipedrive.com/en/article/email-templates) ), but the help article doesn’t say whose templates a given role can move or delete. Check what yours allows before the first cleanup.
2. Find the near-copies: same purpose, slightly different names. Keep the one with a proper name and an owner who still works here. Anything worth saving from the others moves into the original, then each author deletes their own copy.
3. Check every name against the rule. A shared template without a purpose, a moment and an owner in its name gets renamed by its owner this week or deleted by its author.
4. Check that each template’s merge fields are still ones the team reliably fills. A field that dropped off the stage checklist means rewording.
5. Move the three or four templates the team sends most to to the top, if your role can reorder them. New reps pick from the top.
6. Post one line in the team channel: what was removed, renamed, and who owns what. It doubles as the onboarding note for the next hire.

The first cleanup takes longer, because its also the first time anybody has looked.

## When personal templates are enough

If you are two people, skip all of this. Keep templates private and steal each other’s good lines. A naming rule for two authors is a ceremony.

The shared library starts earning its keep at three or four reps. It becomes necessary the first time someone sends a template whose author they couldn’t name. From then on it needs an owner and a rule, or it turns into the picker from the top of this piece. Teams on HubSpot face the same choice as [snippets vs templates in HubSpot](https://salesbond.app/blog/hubspot-snippets-vs-templates-shared-library/).

We build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. It doesn’t touch email templates. Its Deal Health product checks every deal against more than 20 rules, and one of the rule categories is the data on the deal itself. If the field your template leans on is blank on half your open deals, [check your CRM with SalesBond](https://salesbond.app/) before you fix the template.