GitLab

Overview

In the email modal, CiviCRM users can write an email from scratch or use an existing message template. They are given the options to update existing templates or save a new template.

These options are currently available and can be completed by users with basic access to CiviCRM*, even when they do not have the permission CiviCRM: edit message templates.

Organisations want to create standard message templates that cannot be altered by the hundreds of staff using the templates. They need to be able to set this up as a user permission.

Current behaviour

When writing an email in the email modal, CiviCRM users can write an email from scratch or use an existing template. If they write an email from scratch they have the option to save their email as a new message template. If they use an existing template, they have an option to ‘update’ the template or save it as a new message template.

When a CiviCRM user writes an email, selects ‘Save as new template’ and sends the email, a new message template is created. These steps are the same when a user edits an already existing email template.

When a CiviCRM user selects an existing email template, makes changes to the content, selects ‘Update template’ and sends the email, the existing template is updated to whatever content the user has changed.

Email templates can be accessed where the email modal is triggered (e.g. contact record, cases extension etc.).

Expected behaviour

Acceptance criteria:

Any user that does not have the permission to update email templates [CiviCRM: edit message templates] should not see the check box ‘Update Template’

Any user that does not have the permission to create email templates [CiviCRM: edit message templates] should not be able to edit the content of email templates