This documentation is for WSO2 Enterprise Mobility Manager 2.1.0. View documentation for the latest release.
Adding a Policy - Enterprise Mobility Manager 2.1.0 - WSO2 Documentation
Skip to end of metadata
Go to start of metadata

Follow the instructions given below to add a policy:

  1. Sign in to the EMM console.
  2. Click Add under POLICIES to add a new policy.
  3. Select the preferred mobile platform.
  4. Configure the profile:

    A profile in the context of EMM refers to a collection of policies. These policies can be configured using the different configuration options.

    1. Select the policies you wish to add and click CONTINUE.
      Example: Select the policy Restrictions.
    2. Enable the selected policy.
      The selected policy is disabled by default, therefore, click on the on-off switch to enable it.

    3. Select the settings you wish to enable in the selected policy by ticking the respective field or providing the required information.

      If you wish to know more about each policy setting, hover your mouse pointer over the help tip.

      Example: Getting more details on the Allow use of camera setting.

  5. Assign the configured profile of policies to the preferred groups.
    1. Select the device ownership type by clicking on the preferred option from the set device ownership type drop down list:

      BYODBring Your Own Device.
      COPECorporate-Owned, Personally Enabled.
      AnyThe configured profile of policies will be assigned to both the BYOD and COPE device ownership types.
    2. Assign the policy to user roles or users:
      • Assigning user role/s.

        1. Select the set user role/s option.

        2. Select the preferred role from the item list.

          The items that are listed here, are the roles that were added when managing roles through the EMM console.

          For more information, see managing roles.

      • Assigning user/s.
        1. Select the set user/s option.
        2. Enter the characters of the username/s you wish to add, and the system will prompt the users having the names with the characters you entered. You can select the users from the item list.
    3. Select the action that has to be carried out when a device has not complied with a policy.

      In the context of EMM, the following actions are referred to as non-compliance rules. Further, the policies are monitored via the non-compliance rules.

      EnforceForcefully enforce the policies on the assigned groups.

      If the assigned groups do not adhere to the given policies a warning message will be sent.

      MonitorIf the assigned groups do not adhere to the given policies the server is notified of the violation unknown to the user and the administrator can take the necessary actions with regard to the reported.
    4. Click SAVE.
  6. Define a name for the configured profile of policies and a description.

    Set a Name to your Policy is a mandatory field.

  7. Click SAVE to save the configured profile or click SAVE & PUBLISH to save and publish the configured profile as an active policy to the database.

    If you SAVE the configured profile, the policy gets saved in the inactive state. Therefore, the policy will not be taken into account when the WSO2 EMM server filters policies, to enforce a suitable policy on a device that is registered with WSO2 EMM.

    If you SAVE & PUBLISH the configured profile of policies, the policy gets saved in the active state. The active policies are enforced on new devices that enroll with EMM based on the Policy enforcement criteria. If you want to push this policy to the existing devices and want this policy to be applied to the devices, click Apply changes. Then the newly added policy becomes a candidate in the policy selection pool based on the policy enforcement criteria.

  • No labels