# Other Features

This section of the user guide will walk you through the following:

  1. User Profile: explains how to view and manage your personal information in EaaS.
  2. About EaaS: explains how to view information about the EaaS product.
  3. Approvals Pending: explains how to safeguard any environment or collection of environments against unnecessary actions.

# User Profile

The User Settings page lets you control your personal information in EaaS. You can use it to:

  • View your logo, login name, and user role (type).
  • Sign out from the application.
  • Change your username, full name, or email.
  • Change your password.
  • View the user groups you are assigned to.

Simply perform the needed action (e.g., change your username, update your password, etc.), and click Save.

User Profile Page

# About EaaS

To view information about the EaaS product, on the left pane, simply click the About icon.

The information about the EaaS product is displayed.

About Page

To close the window, click the Close icon Close Icon located in its top-right corner.

# Approvals Pending

The EaaS application is equipped with the powerful approval workflow functionality that enables you to safeguard any environment or collection of environments against unnecessary actions. For example, a user wants to deploy an environment. However, the environment will not be deployed until this action is approved by the designated user.

Workflows are not created manually. They are created automatically by the EaaS system whenever a specific triggering event happens (e.g., a user starts deploying an environment, a user stops an environment, etc.).

Here is an example of a simple workflow in EaaS:

  1. A user stops an environment.

  2. A user receives a notification that approval is required. Click Yes to proceed.

    Approval Required Notification

  3. This event triggers the predefined approval workflow to start:

    • The status of the environment changes to Approval Approvals Pending Icon.
    • The assigned approver gets an e-mail notification to approve the command applied to the environment.
  4. A dedicated approver approves or rejects the command applied.

  5. An environment stops/does not stop, depending on the decision made by the assigned approver.

WARNING

Before that, all the major commands in the environment (such as Start, Stop, Deploy, etc.) become temporarily disabled. They get enabled again only after the approver approves or rejects the initiated command.

  1. The workflow ends.

# Approval Process

Before any approval workflow is created and executed, the following operations must be performed in EaaS:

  1. Define the commands, i.e., define the actions that must be approved before they come into force in a certain environment/collection of environments.
  2. Assign approvers, i.e., identify an individual user or several users that must approve the commands made. Only after the command is approved, it comes into force.

# Define Commands

An approval process usually begins with someone doing something to an environment. For example, a user applies new configurations to it, a user stops an environment, etc.

So, to define the command(s) that must be approved before being executed, follow the steps below:

  1. In the EaaS application, locate an environment that must have a certain command defined.
  2. In the top right corner of the contents panel, click the More Actions icon More Actions Icon.
  3. In the list that appears, select the Workspace Settings option.
  4. In the Workspace Settings dialog box that appears, select the Commands Approvals tab.
  5. In the Approval Needed column of the table grid, select the check boxes next to the commands (i.e., actions) that must be approved.
  6. In the Approvals Count column, double-click the field next to the needed command, and set the minimum number of people that must approve the command before it is executed.

WARNING

If the Approvals Count parameter is set to “2”, it means that the command will be executed only after it is approved by two approvers defined.

  1. Click Apply.
KENV EaaS

# Define Approvers

To define the approver(s), follow the steps below:

  1. In the EaaS application, locate an environment that must have a certain command defined.

  2. In the top right corner of the contents panel, click the More Actions icon More Actions Icon.

  3. In the list that appears, select the Workspace Settings option.

  4. In the Workspace Settings dialog box that appears, leave the Permissions tab selected.

  5. In the table grid, locate an individual user, a group of users, a system (equals to all EaaS users), or an owner that must be defined as the approvers. Then scroll to the right and, under the Approval Permission block, grant or deny rights to approve one of the following commands: Apply Configurations, Deploy, Destroy, etc. Simply double-click the needed cell, and select one of the following options:

    • Allow: a user is defined as the “approver”.
    • Deny: a user is not defined as the “approver”.
    • Unset: a default action is applied, i.e., Unset = False, meaning that a user is not defined as the “approver”.
      Workspace Settings Dialog Box
  6. Click Apply.

In case the needed user or user group is not in the list, you can add it manually by doing the following:

  1. Click the Add button and select one of the following options:
    • User: to add an individual user.
    • Group: to add several users in a group.
    • System: to add all EaaS users at once.
  2. Depending on the option selected at a previous step, do one of the following:
    • If the User option has been selected: in the Add User dialog box that appears, select the user(s) you want to grant the default permissions to and click Add.
    • If the Group option has been selected: in the Add Groups dialog box that appears, select the group(s) of users you want to grant the default permissions to and click Add.
    • If the System option has been selected, skip this step.

The newly added user, a group of users, or a system appears in the grid. You can now define them as the approvers as well.

# Perform Approval Actions

In case you are an “approver”, and in case a specific triggering event has happened in the EaaS system (e.g., a user has started a specific environment), you must either approve or reject that action. To do so, follow the steps below:

Option #1. Approval directly from the EaaS application

  1. On the left pane of the EaaS application, select the Approvals Pending option. Alternatively:

    1. Locate the environment pending your approval.
    2. Click the located environment.
    3. In the contents panel, select the Approvals Pending tab.
      Approvals Pending Tab
  2. In the table grid that appears, view the details of the command(s) pending your approval:

    • Date Time: the date and time when the command has been initiated.
    • Environment\Collection (available from the Approvals Pending tab only): the name of the environment where the command has been made.
    • Command: the name of the command pending your approval (e.g., Stop, Start, etc.).
    • Status: the status of the environment where the command pending your approval has been made. In case [0/1] is shown, it means that the command has not been approved yet. After the command is approved, it changes to [1/1], respectively.
    • Affected (available from the Approvals Pending tab only): an informative field to indicate the environment(s) where the command is pending your approval (e.g., “This specific environment”, “All collection environment(s) [5]”, etc.).
    • Requested By: a name of the user who has initiated the command.
  3. In the Status column, click the Take Action button. Alternatively, double-click the record in the table grid.

  4. In the Command request review dialog box that appears, review the detailed information on the command pending your approval and click the button of your choice:

    Command Request Review Dialog Box

  • Approve to approve the command.
  • Decline to reject the command.
  • Cancel request (available for a user who has initiated the approval request only) to quickly cancel the request created accidentally or with errors.
  • Close to close the dialog box and set the resolution action later.

TIP

In case you are an initiator of the command, there is another option for you to cancel your request if needed:

  1. Open your inbox.
  2. Locate an email from EaaS that is sent to you automatically by the system once the command is initiated.
  3. Click the Manage my request option.
  4. In the Command request review dialog box that opens, click the Cancel request option.

Option #2. Approval via E-mail Notification

  1. Open your inbox and locate the e-mail from EaaS to approve a certain command.

  2. Once located, click the Review button.

    E-mail Notification

  3. In the Command request review dialog box that opens, review the detailed information on the command pending your approval and click the button of your choice, Approve or Decline.