Fischer provides a notification engine that allows organizations to send SMTP messages to any member of the Identity ecosystem at any time. The table below lists how notifications can be leveraged by each product feature.
| Product Feature | How are Notifications Used? | Default Notifications |
|---|---|---|
| Approvals | Approval notifications can be initiated from two distinct locations within the product. The approval engine as well as the workflow studio. By default, Fischer covers the majority of the scenarios relating to when an organization may want to notify during the execution of an approval process. | 23 |
| Compliance | 13 | |
| Consolidated | 15 | |
| Duo Authentication | 1 | |
| General | 3 | |
| HPAM | 5 | |
| Mapper | 2 | |
| Password | 11 | |
| Policy | 5 | |
| QR Code | 2 | |
| Resource | Notifications can be employed at the resource level. This notification is typically reserved for resource owners that want to send out a specific email the Beneficiary. This notification should contain information specific to the defined resource. Good information to provide in this email would be links to the application the Identity is now able to access, instructions or training content on how to use the application (or URLs to training videos), any policy, procedural or acceptable use language that may be specific to the allocated resource are all good candidates for information to be sent using this email. | 2 |
| Scheduler | 3 | |
| Self-Service | 27 | |
| SMS | 10 | |
| Workflow | 2 |