Summary
Three new permissions are being introduced to secure the email draft create, edit, and delete endpoints.
Once the change is enabled, each endpoint will require its corresponding permission:
- POST /api/v2/conversations/emails/{conversationId}/draft
Requires: conversation:emailDraft:add
- PATCH /api/v2/conversations/emails/{conversationId}/draft
Requires: conversation:emailDraft:edit
- DELETE /api/v2/conversations/emails/{conversationId}/draft
Requires: conversation:emailDraft:delete
To preserve existing access, all three new permissions will be automatically backfilled to any role that currently has either:
- conversation:email:send
- conversation:email:create
Effective Date
Monday, October 26, 2026
Details
Email draft create, edit, and delete operations were previously not protected by dedicated permissions.
The new permissions provide more granular access control for email draft operations. To ensure existing users retain their current capabilities, the new permissions will be automatically added to roles that already have email send or create access.
Customer Impact
No customer action is required to maintain existing access.
The following permissions will be automatically backfilled:
- conversation:emailDraft:add
- conversation:emailDraft:edit
- conversation:emailDraft:delete
Any role that currently has conversation:email:send or conversation:email:create will receive all three permissions.
As a result, users who can currently create, edit, or delete email drafts will retain that access without interruption.
After the backfill, customers using custom roles can independently add or remove the new permissions to control access to individual email draft operations.
Impacted Resources
POST /api/v2/conversations/emails/{conversationId}/draft
PATCH /api/v2/conversations/emails/{conversationId}/draft
DELETE /api/v2/conversations/emails/{conversationId}/draft
Issue References
PURE-7372
POSTINO-4132
POSTINO-4178
POSTINO-4138
POSTINO-4279
POSTINO-4375
Contacts
@Anish Monikantan Raghavendra Please reply to this announcement with any questions. This helps the wider developer community benefit from the discussion. We encourage you to use this thread before contacting the designated person directly. Thank you for your understanding.