Email Template Folder Access

Why Email Template Folder Access Matters
Email templates are one of the most widely shared assets in a Salesforce org. Sales reps use them to send follow-ups, service agents use them in Email-to-Case replies, and automation (workflow email alerts, Flow email alerts, approval processes) depends on them to communicate with customers. If folder access is misconfigured, the consequences are real: reps cannot find the template they were told to use, marketing-approved wording gets edited by the wrong people, regional teams see templates that do not apply to them, or an email alert silently references a template a user cannot access. The Advanced Administrator exam tests this topic inside the Advanced Security and Access domain because it sits at the intersection of sharing, permissions, and user experience. You are expected to know not just the clicks, but the model: how folder sharing, user permissions, and template type (Classic vs. Lightning) combine to determine what an individual user can actually do.

What Email Template Folder Access Is
Email templates in Salesforce are organized into folders, and access to a template is governed primarily by the sharing settings on the folder that contains it. Think of it like Report and Dashboard folders: the folder is the security container, and the template inherits visibility from it. There are two template frameworks, each with its own folder model:

1. Classic Email Templates (Text, HTML with Letterhead, Custom HTML, Visualforce). These live in Classic folders managed under Setup > Classic Email Templates. Folder-level access options are:
- This folder is accessible by all users
- This folder is hidden from all users
- This folder is accessible only by the following users (shared with Public Groups, Roles, or Roles and Subordinates)
Each Classic folder also has a Public Folder Access setting of Read Only or Read/Write, which controls whether people with access can add or modify templates inside. Every user also has a personal My Personal Email Templates folder that only they can see, and the org ships with an Unfiled Public Classic Email Templates folder visible to all.

2. Lightning Email Templates. These are created in the Email Templates tab in Lightning Experience and use Folders and Enhanced Sharing (enabled in Setup > Lightning Email Templates). Enhanced sharing mirrors the Reports and Dashboards model: you share a folder with Users, Public Groups, Roles, Roles and Subordinates, and Territories, and you assign one of three access levels:
- View: see the folder and use its templates when composing email.
- Edit: everything in View, plus create new templates in the folder and edit existing ones.
- Manage: everything in Edit, plus rename, delete, and share the folder and change other users' access.
Lightning also provides a Private folder for each user and a default Public Email Templates folder visible to everyone. Lightning folders support subfolders, and subfolders inherit sharing from the parent rather than carrying independent sharing settings.

How It Works: The Three Layers
To predict what a user can do with a template, evaluate three layers in order.

Layer 1: User Permissions. These are profile or permission set permissions that act as the gate before folder sharing even matters.
- Manage Public Classic Email Templates: create, edit, delete, and organize Classic public folders and templates owned by others.
- Manage Public Lightning Email Templates: create public Lightning folders, share them, and manage templates not owned by the user.
- Edit HTML Templates: required to create or edit HTML and Visualforce Classic templates (Text templates do not need it).
- Customize Application is additionally needed for Visualforce templates.
Without the relevant Manage permission, a user can still create templates in their own private/personal folder and can use any template in a folder shared with them, but cannot create or share public folders.

Layer 2: Folder Sharing. Once a user has the ability to work with templates at all, folder sharing decides which public folders they can see. In Classic the folder is either open to all, hidden, or restricted to specific groups or roles. In Lightning the user must be granted View, Edit, or Manage either directly or through a group, role, role hierarchy, or territory. Access granted via Roles and Subordinates flows down the role hierarchy, which is the usual way to give a regional VP and everyone under them access to a regional folder. The person who creates a Lightning folder automatically receives Manage access to it.

Layer 3: Template State and Context. A Classic template must be marked Available For Use to appear in pickers. The user interface also matters: in Lightning Experience the email composer can use both Lightning templates and Classic templates, but Salesforce Classic can use only Classic templates. Automation such as workflow email alerts, Flow email alerts, and approval process emails uses Classic templates; the running automation does not evaluate end-user folder access, but the admin configuring the alert must be able to see the template to select it. Features such as Email-to-Case quick actions, list email, and mass email also surface only templates in folders the user can access.

Putting It Together: Typical Design Patterns
- Regional templates: Create a folder per region, share with the regional Role and Subordinates at View access, give the regional sales operations team Edit access, and keep Manage with the admin group.
- Brand-locked templates: Marketing owns a Lightning folder with Manage; all other users get View so they can send but never alter wording.
- Service templates: Share a Support folder with a Public Group of agents at View; share with a Tier 2 group at Edit so senior agents can refine macros and templates.
- Drafting space: Users build drafts in their Private folder, then a user with Edit or Manage on a shared folder moves the template into it when approved.

Troubleshooting Checklist
When a user reports that a template is missing or cannot be edited, check in this order: (1) Which experience are they in, and is the template Classic or Lightning? (2) Is the Classic template marked Available For Use? (3) Is the template in the user's Private folder or someone else's Private folder (private templates are never shared)? (4) Does the user have View, Edit, or Manage on the folder through a user, group, role, role hierarchy, or territory grant? (5) If they are trying to create or share a public folder, do they hold the correct Manage Public Templates permission? (6) For HTML or Visualforce Classic templates, do they have Edit HTML Templates? (7) For subfolders, remember sharing is inherited from the parent.

Exam Tips: Answering Questions on Email Template Folder Access

Tip 1: Identify the template type first. Many questions hinge on whether the scenario involves Classic or Lightning templates. If the question mentions workflow rules, approval processes, email alerts, or Visualforce, it is Classic. If it mentions the Email Templates tab, Enhanced Sharing, subfolders, or View/Edit/Manage access levels, it is Lightning. Answers that mix the two models (for example, applying View/Edit/Manage to a Classic folder) are distractors.

Tip 2: Map verbs to access levels. If the requirement says users should use or send a template, the answer is View. If they should create or modify templates in a shared folder, the answer is Edit. If they should share the folder, rename it, or control others' access, the answer is Manage. Choose the least privilege that satisfies the requirement; the exam favors least-privilege answers.

Tip 3: Separate permission from sharing. If a user cannot create a public folder or cannot edit a template someone else owns, the fix is usually a permission (Manage Public Classic Email Templates or Manage Public Lightning Email Templates), not a folder share. If a user cannot see a folder that exists, the fix is usually folder sharing. If a user cannot create HTML templates specifically, the fix is Edit HTML Templates. Read the symptom carefully to decide which lever to pull.

Tip 4: Prefer groups and roles over individual users. When a scenario describes a department, team, or region, the best-practice answer shares the folder with a Public Group or with Roles and Subordinates, not with named users one at a time. Sharing with Roles and Subordinates is the signal word for anything described as a manager and everyone who reports to them.

Tip 5: Remember what never gets shared. Templates in a user's Private or My Personal Email Templates folder cannot be shared. If the question asks how to make a rep's personal template available to the team, the answer involves moving or copying it into a shared public folder, not changing sharing on the private folder.

Tip 6: Watch for interface mismatches. If a Classic-only user cannot see a template that Lightning users can see, the explanation is that it is a Lightning template, which is invisible in Salesforce Classic. Conversely, Lightning users can see Classic templates, so do not assume Classic templates must be recreated for Lightning.

Tip 7: Subfolders inherit. If a question asks how to give a subset of users access to a subfolder but not the parent, recognize that Lightning subfolders inherit parent sharing, so the correct design is to create a separate top-level folder with its own sharing.

Tip 8: Eliminate over-engineered answers. Options that suggest using Apex, custom objects, record-level sharing rules, or field-level security to control template visibility are wrong. Email template visibility is handled by folder sharing plus template permissions, period. Likewise, modifying the org-wide default or the role hierarchy just to hide a template is a red flag.

Tip 9: Think about who configures automation. If an admin cannot select a template in an email alert, the admin needs access to the Classic folder containing it. End users receiving or triggering the alert do not need folder access for the automation to send.

Sample Question Walkthrough
The EMEA sales team needs to use a set of approved templates, the EMEA sales operations analyst must be able to update those templates, and only the Salesforce admin should control who can see the folder. Users outside EMEA must not see the templates. What should the administrator do?
Reasoning: Create a Lightning email template folder for EMEA. Share it with the EMEA Sales role and subordinates at View (use only). Share it with the sales operations analyst (or a public group containing them) at Edit (update templates). The admin, as folder creator, retains Manage. Do not share with the entire org and do not grant the analyst Manage, since that would let them change sharing. This answer applies least privilege, uses role-based sharing for the team, and matches each requirement to the correct access level.

Key Takeaways
- Folder sharing, not the template record, controls visibility.
- Classic folders use accessible to all / hidden / specific groups and roles with Read Only or Read/Write; Lightning folders use Enhanced Sharing with View, Edit, and Manage.
- Manage Public Classic Email Templates and Manage Public Lightning Email Templates gate the ability to create and administer public folders; Edit HTML Templates gates HTML and Visualforce Classic templates.
- Private folders are never shared; Lightning subfolders inherit parent sharing.
- Lightning can use both template types; Classic uses only Classic templates; automation uses Classic templates.
- On the exam, match the verb in the requirement to the access level, pick the least privilege that works, and share with groups or roles rather than individuals.