Skip to main content

Feature Request: Separate “Email Write” and “Email Send” Permissions in FCRM

I’d like to suggest a permission enhancement for FluentCRM that I believe would significantly improve team workflows and reduce operational risk.

Currently, there is no clear distinction between writing emails (drafting campaigns) and sending them. The existing permission structure creates a gap:

  • You can grant Email Template Manage, which allows someone (e.g., a contractor or copywriter) to create templates
  • But that same person cannot create campaign drafts for review
  • The only way to enable draft creation is by granting Email Send/Write permissions, which also allows sending emails - and that introduces unnecessary risk

This setup makes it difficult to implement a proper editorial workflow, where:

  • A team member drafts campaigns
  • A senior/editor reviews and approves
  • Only authorized users can actually send

Suggested solution:
Introduce a more granular permission system, for example:

  • Email Write (Draft Only) → Can create/edit campaigns but not send
  • Email Send → Can send campaigns
  • (Optional) Approval flow or role-based restrictions

This would align much better with real-world team structures and reduce the risk of accidental or unauthorized sends.

Question to the community:
How are you currently handling this internally?
Are you using any workaround to safely delegate campaign drafting without exposing send permissions?

Would love to hear how others are solving this!

cc: Shahjahan Jewel 

Gavin

#littlethings make #bigthings Shahjahan Jewel