Notification Configuration

To use Notification Triggers in Pleasant Password Server, you can:

  • Define Triggers - to specify the events that cause notifications
  • Setup Notifications - based on these Triggers, on Entries/Folders

1. Define Trigger(s)

Triggers are combinations of events that could fire. They can be re-used when setting up Notifications in Entries/Folders. There are two Triggers setup by default:

  • Full Changes - No View: Most actions are set true, except for View actions and a few others
  • Password Use: Just two Password options are set true, the rest are false

Adding Triggers

You can add new Triggers, grouping similar action types (for example, the following Triggers). Or perhaps you will like to combine them differently and create other unique combinations.

(Only values shown are true, rest are false)

Add Trigger:  

                    

Delete Trigger:

                 

Modify Trigger:

       

Move Trigger:

                  

View Trigger: 

           

                         

Editing Triggers

Allows changing the name and selecting which events will notify the Recipients.

Deleting Triggers

Notification Triggers that are currently In Use cannot be deleted.

2. Setup Notifications

Notifications are activated by the action of a Triggering Role/User on an Entry or Folder. The Notification email is then sent to Recipient Roles/Users.

Note: Notifications setup on folders will be inherited by all its entries and subfolders.

Select an Entry or Folder, and using the Action button or right-click menu, select “Notifications”:

    

The Notification Configuration Window opens:

Clicking “Add Notification” in the bottom left will expand and show the configuration fields:

Configurable Settings

Name: This is the name of the Notification, used to describe what happened, and also is sent in the email subject-line. It defaults to the name of the entry or folder.

  • Recommended: Rename to something unique/descriptive to differentiate it from other possible Notifications on the same entry or folder.

Notification Trigger: A drop down menu to select the desired Notification Trigger that contains the criteria for which actions will cause an email to be sent.

Recipient Roles: The Roles that will receive an email Notification. This will compile a list of ALL users of the selected Roles and any of their Sub-Roles. This field should be used with caution. In the event that users belong to more than one of the selected Roles, each user will only receive 1 email.

Recipient Users: The individual users that will receive an email Notification. In the event that a user is entered here and a Role they belong to is entered in the Recipient Roles, they will still only receive 1 email.

Triggering Roles: The Roles that will activate the Notification Trigger. For all users that are members of a selected Triggering Role, if they successfully complete any of the actions defined within the Notification Trigger on the corresponding entry or folder, a Notification will be generated and sent out.

Triggering Users: The individual users that will activate the Notification Trigger. If any of the selected Triggering Users complete any of the actions defined within the Notification Trigger on the corresponding entry or folder, a Notification will be generated and sent out.

Multiple Notifications for the same Entry/Folder

You can create multiple Notification Triggers that activate based on different Triggers.

Recipients will only receive one email for a single action on an entry/folder, even if they are included in more than one activated trigger. The emails will be combined and show the results of both Triggers firing.

Notifications on Folders

Rather than setting up notifications on every entry/subfolder, a user can create Notifications on the whole folder.

Note: Notifications setup on folders will be inherited by all its entries and subfolders.

The Notification rules will be applied to all the entries within the Folder, all Sub-Folders, and all Entries within the Sub-Folders). Because of this you could get more Notifications than intended.

One should be careful placing Notifications on the “Root” directory.

Note: The Block Inheritance feature will also block inheritance of Notification rules.
This prevents admin from receiving notifications from credentials that they would not know exist.

Tag page
You must login to post a comment.