Using E-mail Notifications for Provisioning Requests
Provisioning workflow participants can receive e-mail notifications when a request is submitted, waiting for approval, approved, cancelled, rejected, or is unsuccessful. You can allow the following workflow participants to receive e-mail notifications:
All workflow participants. Users, Request Approvers, Token Distributors
Super Admin
Workflow participants in parent security domain
You can add a comment to the request properties configuration that will be included in the e-mail notification, for example, to explain why a request is denied.
Before AM can send e-mail notifications, you must configure SMTP. For more information, see Configure the SMTP(s) Mail Service.
If you enable e-mail notifications to workflow participants in the parent security domain, all Request Approvers and Token Distributors in security domains above the security domain where a request originates receive workflow e-mail notifications.
You can deselect the default setting that enables workflow e-mail notifications to all workflow participants (Users, Request Approvers, Token Distributors). You cannot disable workflow e-mail notifications by participant type, except for Super Admin.
Related Tasks
Related Articles
Customize E-mail Notifications 68Number of Views Configure E-mail Notifications for Self-Service User Account Changes 61Number of Views Email Notifications are not using Default Email Account in RSA Identity Governance and Lifecycle 6.x and 7.0 74Number of Views KRA cannot reach SMTP server to send email notifications 26Number of Views Resend E-mail to Users 3Number of Views
Trending Articles
Change Requests stuck in the AFX Fulfillment Handler Workflow Node and Workflows Stalled in RSA Identity Governance & Life… Collector Stuck in Data Collection Phase with "Sent Request to Agent Hosting the Collector" RSA Authentication Manager 8.9 Patches and Hotfixes Readme How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Workflows stuck in AFX fulfillment and/or Provisioning nodes in RSA Identity Governance & Lifecycle