Genesys Cloud - Developer Announcements!

 View Only

Sign Up

  • 1.  New Permissions Required for Email Draft Endpoints

    Posted 09-18-2026 06:56

    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.



  • 2.  RE: New Permissions Required for Email Draft Endpoints
    Best Answer

    Posted 09-23-2026 09:13

    Update to this announcement - correction to the backfill criteria:

    The three new permissions will be automatically backfilled only to roles that
    currently have:

      • conversation:email:create

    conversation:email:send is no longer part of the backfill criteria. The earlier
    version of this announcement stated that either conversation:email:send or
    conversation:email:create would qualify a role for the backfill - that is no
    longer the case.

    Everything else in the announcement is unchanged:

      • POST   /api/v2/conversations/emails/{conversationId}/draft
                → conversation:emailDraft:add
      • PATCH  /api/v2/conversations/emails/{conversationId}/draft
                → conversation:emailDraft:edit
      • DELETE /api/v2/conversations/emails/{conversationId}/draft
                → conversation:emailDraft:delete

    Effective date remains Monday, October 26, 2026.

    Customer impact: if you use custom roles that grant conversation:email:send but
    not conversation:email:create, those roles will not receive the new email draft
    permissions automatically. Please review those roles before the effective date
    and add conversation:emailDraft:add / :edit / :delete where email draft access
    is required.

    Apologies for the confusion - please reply here with any questions.



    ------------------------------
    Anish Monikantan
    Software Engineer
    ------------------------------



  • 3.  RE: New Permissions Required for Email Draft Endpoints

    Posted 09-24-2026 15:43

    Hi @Anish Monikantan Raghavendra!

    Thanks for the heads-up.



    ------------------------------
    Juliano Fernandes Mendes Pimentel De Paiva
    Genesys Analyst
    ------------------------------



  • 4.  RE: New Permissions Required for Email Draft Endpoints

    Posted 09-24-2026 15:42

    Hello Developer Community!


    We ran into some issues a short while ago. Team members were unable to attach files to email interactions.

    We added the `conversation:emailDraft:add` permission, and the issue was resolved.





    ------------------------------
    Juliano Fernandes Mendes Pimentel De Paiva
    Genesys Analyst
    ------------------------------



  • 5.  RE: New Permissions Required for Email Draft Endpoints

    Posted 09-25-2026 16:28

    Thank you.



    ------------------------------
    Camila Meneghini
    ------------------------------