Emails permissions
Access to Emails is simpler than most modules, and more permissive. Membership of the service is the only test.
One level, not three
Section titled “One level, not three”Every operation in the module — listing, opening, creating, editing, duplicating, deleting — requires the same thing: that you are a member of the service.
There is no viewer-versus-editor split here. A member who can see the module can also change and delete anything in it.
That is worth knowing if you are used to other modules. In Dashboards, for instance, deleting needs an owner or admin. In Emails, any member can delete any email the service owns.
Membership comes either from being a service member directly or from belonging to a team attached to the service. Someone holding the platform-level system_admin role bypasses the check entirely; the ordinary platform admin role does not — service access here is strictly membership-based.
What each person can do
Section titled “What each person can do”| Operation | Who |
|---|---|
| See the email list | Any service member |
| Open and read an email | Any service member |
| Create an email | Any service member |
| Edit blocks, styles, and settings | Any service member |
| Duplicate an email | Any service member |
| Delete an email | Any service member |
| Save and use snippets | Any service member |
| Save to the template library | Any service member |
| Create and revert versions | Any service member |
| Send a test | Any service member |
System templates are the exception
Section titled “System templates are the exception”Templates marked System ship with the platform and belong to no service. Nobody can edit or delete them from inside a service, whatever their role.
They can be duplicated, and the copy belongs to your service and behaves like anything else in this table.
Sending is somewhere else
Section titled “Sending is somewhere else”These permissions cover building emails. Sending one to a real list happens in Marketing, under whatever rules that module applies.
The practical effect is that being able to build an email is not the same as being able to send it to customers. A member can produce a finished template and still need someone else to run the campaign.
Related
Section titled “Related”Create an email covers the module page and what the card buttons do. Troubleshooting covers what an access failure looks like.