Notification Types

In this document, you’ll learn about the different notifications available in Zluri. For each notification type, we’ll cover the following fields:

1. Description / condition for receiving the notifications (e.g., Raised access request doesn't match automation rules)
2. Delivered via: Where you'll receive them (email, Slack, and/or in-app)
3. Sent to: Which user roles receive each notification type (Admin, Owner, Finance Admin, Reviewer, etc.)
4. Sent / can be generated by: Which user roles can send or generate each notification type (if different from receiver)
5. Frequency, if applicable.

Manage your notifications

To view and configure notifications types in Zluri:

1. Go to Settings → Notifications.
2. Select the notification types you want to receive. Changes are saved automatically.

Notification categories

Zluri supports the following notification types and sub-types:

📘

You can also view notification categories and details in this reference table.

Access Reviews Updates and Reminders

• Review start date notification to certification owner
  • Delivered via: Email, Slack
  • Sent to: Certification Owner
• Review start date notification to reviewers
  • Delivered via: Email, Slack
  • Sent to: Assigned reviewer(s)
• A review task has been delegated to a new reviewer
  • Delivered via: Email, Slack
  • Sent to: Assigned reviewer(s)
• An application's review moved from previous level to current level
  After completion of an application’s level 1 review, all level 2 reviewers get notified
  • Delivered via: Email, Slack
  • Sent to: Reviewer(s) of current level
• Manual review reminder sent by certification owner or Zluri admin
  • Delivered via: Email, Slack
  • Sent to: Assigned reviewer(s) with pending review(s)
• Review deadline approaching (48 hours or less remaining) for reviewers
  • Delivered via: Email, Slack
  • Sent to: Assigned reviewer(s) with pending reviews
  • When: Certification is 48 hours away from review end date
• Review deadline approaching (48 hours or less remaining) for certification owner
  • Delivered via: Email, Slack
  • Sent to: Certification Owner
  • When: Certification is 48 hours away from review end date
• Review end date reached with pending reviews
  • Delivered via: Email, Slack
  • Sent to: Certification Owner
• Remediation deadline approaching (48 hours or less remaining) with pending actions for certification owner
  • Delivered via: Email, Slack
  • Sent to: Certification Owner
  • When: Remediation is 48 hours away from remediation end date
• An upcoming recurring certification is based on playbook(s) that have been deleted or unpublished
  • Delivered via: Email, Slack
  • Sent to: Admin, Owner, Certification Owner
• PDF report of all details of a requested certification
  • Delivered via: Email
  • Sent to: User who generated the report, Certification Owner
• Certification created successfully
  • Delivered via: In-app
  • Sent to: Certification Owner
• Review successfully signed off
  • Delivered via: In-app
  • Sent to: Certification Owner
• Review completed successfully
  • Delivered via: In-app
  • Sent to: Certification Owner

---

Access requests approval actions updates

• A request is awaiting approval from the assigned approver
  • Delivered via: Email, Slack
  • Sent to: Approvers
• Access request is pending approval action
  • Delivered via: Email, Slack
  • Sent to: Approvers
• Displayed to approvers when they successfully approve the request from the Slack notification and notification is sent to the next approver
  • Delivered via: Slack
  • Sent to: Approvers
• Displayed to approvers when they successfully reject the request from the Slack notification
  • Delivered via: Slack
  • Sent to: Approvers
• Access request approved and provisioning action has been triggered
  • Delivered via: Email, Slack
  • Sent to: Requester
• Access request approved and provisioning is completed
  • Delivered via: Email, Slack
  • Sent to: Requester
• Access request rejected
  • Delivered via: Email, Slack
  • Sent to: Requester
• Deprovisioning action completed for a request
  • Delivered via: Email, Slack
  • Sent to: Requester
• Comment posted on an access request
  • Delivered via: Email, Slack
  • Sent to: Requester, Approvers

---

Approval action updates

• Request is auto-rejected by an automation rule set up by a Zluri admin
  • Delivered via: Email, Slack
  • Sent to: Requester

---

Optimization recommendations and alerts

• Notification sent to users to confirm whether they wish to keep or forego a particular license

  • Delivered via: Email

  • Sent to: Target users

    

• List of optimizable licenses for application

  • Delivered via / Sent to:

    • Email: App Owner, App IT Owner, App Financial Owner

    • Slack: App Owner

      

---

Export notifications

These notifications relate to exporting data from Zluri.

• Notification with the exported file as an attachment
  • Delivered via: Email, in-app
  • Sent to: User who requested the report
  • Sent / can be generated by: Admin

---

Spend management alerts

• Reminder to add latest transactions

  • Delivered via: Email

  • Sent to: Admin

    

• Transaction Rule execution failed

  • Delivered via: In-app
  • Sent to: User who executed the rule
  • Sent / can be generated by: Admin

• Forced rule execution results for unrecognized transactions

  • Delivered via: In-app
  • Sent to: User who executed the rule
  • Sent / can be generated by: Admin, Owner, IT Admin, Finance Admin, Procurement Admin, Integration Admin, Security Admin

• Information of recognized transactions on which the execution was performed

  • Delivered via: In-app
  • Sent to: User who executed the rule
  • Sent / can be generated by: Admin, Owner, IT Admin, Finance Admin, Procurement Admin, Integration Admin, Security Admin

• Information of all transactions on which the execution was performed

  • Delivered via: In-app
  • Sent to: User who executed the rule
  • Sent / can be generated by: Admin, Owner, IT Admin, Finance Admin, Procurement Admin, Integration Admin, Security Admin

• List of applications found with increased spends in the current month

  • Delivered via: In-app
  • Sent to: Admin

---

Integration notifications

These are the basic rules for integration-related notifications. For a more comprehensive view, check out the dedicated document.

• List of applications that can be integrated with Zluri
  • Delivered via: Email
  • Sent to: Admin

---

Application discovery notifications

• List of applications discovered in the last 24 hours
  • Delivered via: Email
  • Sent to: Admin, Owner

---

Restricted app usage alerts

• List of restricted apps with largest number of active users

  • Delivered via: In-app
  • Sent to: Admin

• Restricted applications usage alert along with list of users using the restricted applications

  • Delivered via: Email

  • Sent to: Admin

    

• Notification to employees to stop using restricted applications

  • Delivered via: Email

  • Sent to: Admin, Affected employees

  • Sent / generatable by: Admin

    

---

License and contract management alerts

• Sent to employees regarding cancel by or end date of contract

  • Delivered via: Email

  • Sent to: Contract Owner, Contract Finance Owner, Contract IT Owner, App Owner, App IT Owner, App Finance Owner

  • When: 60, 30, 15, and 1 day(s) before the contract cancel by or end date

    

• Upcoming payment date for contract

  • Delivered via: Email

  • Sent to: Contract Owner, Contract Finance Owner, Contract IT Owner, App Owner, App IT Owner, App Finance Owner

  • When: 7 days and 1 day before payment date

    

• Sent to employees regarding true-up date of contract

  • Delivered via: Email
  • Sent to: Contract Owner, Contract Finance Owner, Contract IT Owner, App Owner, App IT Owner, App Finance Owner
  • When: 15 days before the first true-up date
    

• Upcoming contract renewal/end date

  • Delivered via: Email
  • Sent to: Contract Owner, Contract Finance Owner, Contract IT Owner, App Owner, App IT Owner, App Finance Owner
  • When: 7 days before the end date
    

• Contract added as draft

  • Delivered via: In-app
  • Sent to: User who added the draft
  • Sent / can be generated by: Admin

• Bulk license mapping successful

  • Delivered via: In-app
  • Sent to: User who did the bulk mapping
  • Sent / can be generated by: Admin

---

Access requests reminders

• Shows approvers how many requests are pending their review
  • Delivered via: Email, Slack
  • Sent to: Assigned approver(s)
  • Frequency: Every 24 hours at 12:00 am UTC (configurable on request)

---

Access requests admin alerts and updates

• Raised access request doesn't match automation rules
  • Delivered via: Email, Slack
  • Sent to: Admin, Owner
• Deprovisioning action for access request deleted or unpublished
  • Delivered via: Email, Slack
  • Sent to: Admin, Owner
• Provisioning action for access request deleted or unpublished
  • Delivered via: Email, Slack
  • Sent to: Admin, Owner

---

Notification reference table

📘

The table below might be too wide to fit on certain screens. Scroll horizontally to see all columns.