Ask Search:
Joe MascioccoJoe Masciocco 

Is it possible to stop all email notifications to one particular user? Thanks!

 We get email notifications for lots of different occurances, every time something changes in an opportunity really - which is a lot.  One of the sales people wants to stop getting all notifications, how can I set this up for her?

Thanks!
Best Answer chosen by Moderator (salesforce.com) 
Steve MolisSteve Molis
You want Section 3.f  -> 

Creating Email Alerts for Workflow, Approvals, or Milestones

Available in: Enterprise, Unlimited, and Developer Editions

User Permissions Needed
To create or change workflow rules:“Customize Application”
To create or change email alerts:“Customize Application”
To create email alerts:
  1. For workflow and approvals, click Your Name | Setup | Create | Workflow & Approvals | Email Alerts.

    For milestones on entitlement processes, click Your Name | Setup | Customize | Entitlement Management | Entitlement Processes, choose an entitlement process, a milestone, and click Add Workflow Action.

  2. Click New Email Alert.
  3. Configure the email alert:
    1. Enter a description for this email alert.
    2. Enter a unique name to refer to this component in the Force.com API and to prevent naming conflicts for managed package installations. The requirement for uniqueness is only within the selected object type. You can have actions of the same type (for example, two email alerts) with the same unique name, provided they are defined for different objects, such as one for Campaigns and one for Opportunities. The Unique Name field can contain only underscores and alphanumeric characters. It must be unique within the selected object type, begin with a letter, not include spaces, not end with an underscore, and not contain two consecutive underscores.
    3. If available, choose the object for this email alert.

      Salesforce uses this object when generating merge field values for email templates with workflow rules and approval processes. Also, you can define the recipients of this email alert using contact and user lookup fields that are relevant to that object. For example, if you select Contract, you can define the contract signer as a recipient. The object is read-only if the new email alert is associated with an approval process or workflow rule for a particular object.

      Tip
      To create workflow rules for case comments so that comments added to cases send email alerts when a rule is triggered, select Case Comment in the Object drop-down list when creating a new workflow rule.
    4. Choose an email template.Note
      If the email template you choose contains approval merge fields named {!ApprovalRequest.field_name}, these fields will return values only when that email template is used as the approval assignment template. If you use the template for any other email alert action—in either workflow rules or approval processes—the merge fields will return a null value.
    5. Optionally, select Protected Component to mark the alert as protected if it is part of a Managed - Released Managed - Released package.
    6. Select who should receive this email alert. Depending on your organization settings and the object you selected, some options in this list may not be available.
      • Account Owner—The user listed as the account owner of either the account itself or the account associated with the record. This option only works for email alerts on accounts, opportunities, cases, contacts, contracts, and any custom object that is a child of the account object. Also, an account owner must be specified for the associated account. If you select another type of object or the associated account does not have an account owner, Salesforce sends the email alert to the record owner instead.
      • Account Team—All users assigned to a particular account team role. Note
        The Account Team option is always available; however, emails are only sent when the rule is associated with the account object or any of its immediate child objects.
      • Case Team—All users assigned to a particular case team role.
      • Creator—The user who created the record.
      • Customer Portal User—All users associated with a Customer Portal.
      • Email Field—An email address field on the selected object, such as the Email field on lead records or custom email fields.Note
        When creating email alerts for campaign members, Email Field refers to the email field on the lead or contact that the campaign member is based on.
      • Owner—The record owner.
      • Partner User—All users associated with a partner portal.
      • Portal Role—All users assigned to a particular portal role.
      • Portal Role and Subordinates—All users assigned to a particular portal role, plus all users in roles below that role.
      • Public Groups—The users in a particular public group.
      • Related Contact—An associated contact on the record. For example, you can select the Customer Signed By field for contracts that contain the name of the contract signer.
      • Related Lead or Contact Owner—A campaign member's lead or contact owner.
      • Related User—An associated user on the record. For example, contract records have an Activated By field that contains the name of the user that activated the contract.
      • Role—All of the users assigned a particular role.
      • Role and Internal Subordinates—All users in a particular role, plus all users in roles below that role, excluding partner portal and Customer Portal users.
      • Role and Subordinates—All users in a particular role, plus all users in roles below that role.
      • User—A particular user.
      • Sales Team—A member of the sales team. This option doesn't appear unless you have team selling enabled for your opportunities. Note
        The Sales Team option only works for email alerts configured for opportunities. It does not work for email alerts configured for child objects of opportunities.

      The recipients that match your search results appear in the Available Recipients list.

    7. Select the recipients who should receive this email alert in the Available Recipients list and click Add.Note
      If you change the object after selecting recipients, Salesforce clears the Selected Recipients list.
    8. Optionally, enter up to five additional email addresses.
    9. Optionally, change the From Email Address to:
      • The email address of the default workflow user.
      • A previously configured and verified organization-wide address. This allows you to use a standard global email address for your organization (such as support@company.com) instead of the default From field, which is the email address of the person who updates the record.

        Only verified organization-wide email addresses display in the From Email Address picklist.

      Note
      If you select Make this the default From email address for this object's email alerts, it overrides the From Email Address for all email alerts associated with that object. Upon saving, a dialog box prompts you to confirm your selection. You can still customize individual email alerts to use a different From Email Address.
    10. Click Save.
    Note
    If your email recipient is a record owner and the owner of the record is a queue, the queue email receives the email alert. If the queue is set up so that email is sent to all members, queue members are notified as well. If no queue email is specified, only queue members are notified.
  4. To set email alerts into action, associate them with a workflow rule, approval process, or entitlement process.
Note
The daily limit for emails sent from workflow and approval-related email alerts is 1,000 per standard Salesforce license per organization. The overall organization limit is 2 million. When the daily limit is reached, a warning email goes out to the default workflow user. If the default workflow user isn't set, then the warning email is sent to an active system administrator. For more information, see Workflow Daily Email Limit.

All Answers

Steve MolisSteve Molis
 You can change the distribution list to exclude a specific User or  Role.
Joe MascioccoJoe Masciocco
 Thanks SteveMo, would I have to do to amend the distribution list on every account/opp/contact that she's attributed to though?  That could be cumbersome. 
Steve MolisSteve Molis
 No, you would just need to update the Workflow Email Alerts (I'll have something posted in a sec.) 
Steve MolisSteve Molis
You want Section 3.f  -> 

Creating Email Alerts for Workflow, Approvals, or Milestones

Available in: Enterprise, Unlimited, and Developer Editions

User Permissions Needed
To create or change workflow rules:“Customize Application”
To create or change email alerts:“Customize Application”
To create email alerts:
  1. For workflow and approvals, click Your Name | Setup | Create | Workflow & Approvals | Email Alerts.

    For milestones on entitlement processes, click Your Name | Setup | Customize | Entitlement Management | Entitlement Processes, choose an entitlement process, a milestone, and click Add Workflow Action.

  2. Click New Email Alert.
  3. Configure the email alert:
    1. Enter a description for this email alert.
    2. Enter a unique name to refer to this component in the Force.com API and to prevent naming conflicts for managed package installations. The requirement for uniqueness is only within the selected object type. You can have actions of the same type (for example, two email alerts) with the same unique name, provided they are defined for different objects, such as one for Campaigns and one for Opportunities. The Unique Name field can contain only underscores and alphanumeric characters. It must be unique within the selected object type, begin with a letter, not include spaces, not end with an underscore, and not contain two consecutive underscores.
    3. If available, choose the object for this email alert.

      Salesforce uses this object when generating merge field values for email templates with workflow rules and approval processes. Also, you can define the recipients of this email alert using contact and user lookup fields that are relevant to that object. For example, if you select Contract, you can define the contract signer as a recipient. The object is read-only if the new email alert is associated with an approval process or workflow rule for a particular object.

      Tip
      To create workflow rules for case comments so that comments added to cases send email alerts when a rule is triggered, select Case Comment in the Object drop-down list when creating a new workflow rule.
    4. Choose an email template.Note
      If the email template you choose contains approval merge fields named {!ApprovalRequest.field_name}, these fields will return values only when that email template is used as the approval assignment template. If you use the template for any other email alert action—in either workflow rules or approval processes—the merge fields will return a null value.
    5. Optionally, select Protected Component to mark the alert as protected if it is part of a Managed - Released Managed - Released package.
    6. Select who should receive this email alert. Depending on your organization settings and the object you selected, some options in this list may not be available.
      • Account Owner—The user listed as the account owner of either the account itself or the account associated with the record. This option only works for email alerts on accounts, opportunities, cases, contacts, contracts, and any custom object that is a child of the account object. Also, an account owner must be specified for the associated account. If you select another type of object or the associated account does not have an account owner, Salesforce sends the email alert to the record owner instead.
      • Account Team—All users assigned to a particular account team role. Note
        The Account Team option is always available; however, emails are only sent when the rule is associated with the account object or any of its immediate child objects.
      • Case Team—All users assigned to a particular case team role.
      • Creator—The user who created the record.
      • Customer Portal User—All users associated with a Customer Portal.
      • Email Field—An email address field on the selected object, such as the Email field on lead records or custom email fields.Note
        When creating email alerts for campaign members, Email Field refers to the email field on the lead or contact that the campaign member is based on.
      • Owner—The record owner.
      • Partner User—All users associated with a partner portal.
      • Portal Role—All users assigned to a particular portal role.
      • Portal Role and Subordinates—All users assigned to a particular portal role, plus all users in roles below that role.
      • Public Groups—The users in a particular public group.
      • Related Contact—An associated contact on the record. For example, you can select the Customer Signed By field for contracts that contain the name of the contract signer.
      • Related Lead or Contact Owner—A campaign member's lead or contact owner.
      • Related User—An associated user on the record. For example, contract records have an Activated By field that contains the name of the user that activated the contract.
      • Role—All of the users assigned a particular role.
      • Role and Internal Subordinates—All users in a particular role, plus all users in roles below that role, excluding partner portal and Customer Portal users.
      • Role and Subordinates—All users in a particular role, plus all users in roles below that role.
      • User—A particular user.
      • Sales Team—A member of the sales team. This option doesn't appear unless you have team selling enabled for your opportunities. Note
        The Sales Team option only works for email alerts configured for opportunities. It does not work for email alerts configured for child objects of opportunities.

      The recipients that match your search results appear in the Available Recipients list.

    7. Select the recipients who should receive this email alert in the Available Recipients list and click Add.Note
      If you change the object after selecting recipients, Salesforce clears the Selected Recipients list.
    8. Optionally, enter up to five additional email addresses.
    9. Optionally, change the From Email Address to:
      • The email address of the default workflow user.
      • A previously configured and verified organization-wide address. This allows you to use a standard global email address for your organization (such as support@company.com) instead of the default From field, which is the email address of the person who updates the record.

        Only verified organization-wide email addresses display in the From Email Address picklist.

      Note
      If you select Make this the default From email address for this object's email alerts, it overrides the From Email Address for all email alerts associated with that object. Upon saving, a dialog box prompts you to confirm your selection. You can still customize individual email alerts to use a different From Email Address.
    10. Click Save.
    Note
    If your email recipient is a record owner and the owner of the record is a queue, the queue email receives the email alert. If the queue is set up so that email is sent to all members, queue members are notified as well. If no queue email is specified, only queue members are notified.
  4. To set email alerts into action, associate them with a workflow rule, approval process, or entitlement process.
Note
The daily limit for emails sent from workflow and approval-related email alerts is 1,000 per standard Salesforce license per organization. The overall organization limit is 2 million. When the daily limit is reached, a warning email goes out to the default workflow user. If the default workflow user isn't set, then the warning email is sent to an active system administrator. For more information, see Workflow Daily Email Limit.
This was selected as the best answer
Joe MascioccoJoe Masciocco
Great, thank you!!