User Tools

Site Tools


campaign_supervision_workflow

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
Next revisionBoth sides next revision
campaign_supervision_workflow [2016/09/08 19:01] – created lucycampaign_supervision_workflow [2016/09/21 18:05] lucy
Line 1: Line 1:
 ===== Background Info ===== ===== Background Info =====
  
-The supervision'workflow idea is based on the 4-eyes principle when creating a new campaign: a campaign administrator will be responsible for creating a specific phishing or e-learning campaign. But he will only be able to start the campaign after a different user (the supervisor) reviewed the campaign and approved it. If the supervisor rejects the campaign a ticket with an expiry date will be created within the campaign for the administrator. +The approval workflow idea is based on the 4-eyes principle when creating a new campaign: a campaign administrator will be responsible for creating a specific phishing or e-learning campaign. But he will only be able to start the campaign after a different user (the supervisor) reviewed the campaign and approved it. If the supervisor rejects the campaign a ticket with an expiry date will be created within the campaign for the administrator. 
  
 ===== Configuration ===== ===== Configuration =====
  
-  - create a user with the "user" role. You don't need to assign any special rights here.+1. create a user with the "user" role. You don't need to assign any special rights here.
  
 {{ svstep1.png?600 }} {{ svstep1.png?600 }}
  
-  - create a supervisor with "supervisor" role and assign the "user" as a supervised user+2. create a supervisor with "supervisor" role and assign the "user" as a supervised user
  
 {{ svstep2.png?600 }} {{ svstep2.png?600 }}
Line 21: Line 21:
 {{ svstep5.png?600 }} {{ svstep5.png?600 }}
  
-  - If the campaign admin will log in under his "user" role and starts the campaign it will be put on hold, until "supervisor" approves the launch. On this step you can see a new entry created on "Supervision Log". Within the campaign dashboard you will also see a small turning wheel that indicates that the campaign is waiting for approval+3. If the campaign admin will log in under his "user" role and starts the campaign it will be put on hold, until "supervisor" approves the launch. On this step you can see a new entry created on "Supervision Log". Within the campaign dashboard you will also see a small turning wheel that indicates that the campaign is waiting for approval
  
 {{ sv1.png?600 }} {{ sv1.png?600 }}
  
-  - now log in under "supervisor" and go to the same campaign and press a "reject" button - you will see a reject form with comments and all that stuff. If supervisor presses "Approve", the campaign just starts without any comments from supervisor. In both cases (if campaign is approved or rejected) Lucy updates the same supervision log entry created on step 4.+{{ sv2.png?600 }}
  
 +4. If the supervisor now logs in under his "supervisor" role and navigates to the same campaign he will be able to either reject or approve the campaign by clicking on the according buttons:
 +
 +{{ sv3.png?600 }}
 +
 +If the supervisor rejects the campaign he will be able to create a ticket with a end date and severity that allows him to communicate the required changes:
 +
 +{{ sv4.png?600 }}
 +
 +In case of a rejected campaign the campaign admin with his "user" role will be able to see the desired changes within the supervision log:
 +
 +{{ sv5.png?600 }}
 +
 +{{ sv6.png?600 }}
 +
 +Once the changes have been done the step 4 can be repeated again until the supervisor approves the campaign
campaign_supervision_workflow.txt · Last modified: 2019/07/25 12:49 by 127.0.0.1