---
title: "Security & Permissions Considerations"
description: "Because mass emailing carries risk, it’s important to control who can trigger sends and how. --- ## Front‑End Trigger Forms - Safest way to let non‑admin staff send campaigns. - Embed the Master Control Notification Form on a hidden front‑end…"
url: "https://brightleafdigital.io/docs/security-permissions-considerations/"
updated: "2026-10-18"
category: "Mass Email Notifications for Gravity Forms / Explanations & Concepts"
---

# Security & Permissions Considerations

Because mass emailing carries risk, it’s important to control who can trigger sends and how.

---

## Front‑End Trigger Forms

- Safest way to let non‑admin staff send campaigns.
- Embed the Master Control Notification Form on a hidden front‑end page.
- Restrict access so only trusted roles can see and submit it.

---

## Role Restrictions

- Use a role editor or membership plugin to limit access by capability.
- Prevents unauthorized users from seeing or editing form settings.

---

## No Backend Access

- Staff should not need access to Gravity Forms feeds or settings.
- Keep those in admin control to avoid misconfiguration.

---

## Audit & Logging

- All sends are logged on entries and in batch details.

---

By setting clear permission boundaries and using front‑end trigger forms, you can safely delegate sending while protecting your site and reputation.
