Career
sharepoint based solutions
user registration management
Kairaus’ User registration request management workflow solution integrates requestor, help desk & the IT department of an organization. The workflow is developed on ShapePoint platform.

Kairaus’ User registration request management workflow solution integrates requestor, help desk & the IT department of an organization. The workflow is developed on ShapePoint platform.

Some of the key highlights of the solution are:

I. Stages

The 2 stage workflow is created with each workflow having 2-3 checkpoints

  1. Initial Approver Workflow
  2. Compliance Team Workflow

Initial Approver Workflow

  1. An e-mail would be sent to the approver team with the link, which would direct the members of the approving team
  2. Status would be updated for the respective registration request. Statuses would be as follows:
    1. Approved & sent to Compliance Team
    2. Escalated
    3. Iteration
    4. Cancelled
Compliance Team Workflow

The Compliance team will update the status as:

  1. Approved & Sent to IT Service Desk
  2. Expired
  3. Iteration
  4. Cancelled
  5. Escalated
  6. Iteration
  7. Cancelled
  1. Approved & Sent to IT Service Desk
    1. An e-mail is sent to the IT Service Desk with the link to access the form.
    2. At this stage, an e-mail is sent to the requestor also to update him on the status of the form

  2. Expired
    1. After 5 days, if no action has been taken on the request, the link in the e-mail will expire.
    2. An e-mail would be sent to the requestor & the Reporting Manager to update on the status.

  3. Iteration
    1. The compliance team would record their comments or feedbacks in the column provided.
    2. An e-mail would be sent to the requestor to carry out the modifications & resubmit the form.
    3. An e-mail would be sent to the initial approver to inform about the modifications required.
    4. The e-mail would contain the link to access the form.
    5. The process would restart from the approval seeking from the initial approver. 

  4. Cancelled
    1. The compliance team would record their comments or feedbacks in the column provided.
    2. An e-mail would be sent to the requester & initial approver to update them about the status.
    3. The e-mail would contain the link to access the form.

  5. Escalated
    1. After 5 days, if no action has been taken on the request, the e-mail would automatically be forwarded to the alternate approver or supervisor & the link in the e-mail would be sent to the initial approver would expire.
    2. If the alternate approver or supervisor is not defined, then an e-mail would be sent to the requestor to re-submit the form & the link in the e-mail would be sent.
    3. A re-submit tab would be provided & the workflow would re-start.

  6. Iteration
    1. The initial approver would record their comments or feedbacks in the column provided.
    2. An e-mail would be sent to the requestor to carry out the modifications & resubmit the form.
    3. The e-mail would contain the link to access the form.
    4. The process would restart. 

  7. Cancelled
    1. The initial approver would record their comments or feedbacks in the column provided.
    2. An e-mail would be sent to the requester to update them about the status.
    3. The e-mail would contain the link to access the form.
Initial Approver Workflow
  • An e-mail would be sent to the approver team with the link, which would direct the members of the approving team
  • Status would be updated for the respective registration request. Statuses would be as follows:
    1. Approved & sent to Compliance Team
    2. Escalated
    3. Iteration
    4. Cancelled