PingOne

Cloning a rule

Cloning an existing provisioning rule reduces repetitive configuration, minimizes manual entry errors, and repurposes complex logic for different groups or attributes.

Cloning a rule can be beneficial in the following situations:

  • Onboarding new applications: Quickly set up a new application that requires the same mappings as an existing one. You can then make minor adjustments, such as a different target connection or a specific group filter, as needed.

  • Safe testing and improvement: Safely test new changes, such as mapping or filter improvements, by cloning a rule that’s already in use. This lets you try out ways to fix errors or make things run faster without changing your current setup.

You can only clone rules within the same environment.

Steps

  1. In the PingOne admin console, go to Integrations > Provisioning.

  2. On the Rules tab, find the appropriate rule and click the More Options (⋮) icon.

  3. Click Clone Rule and then click Continue in the confirmation modal.

    PingOne allows only one enabled inbound rule with a specific configuration at a time.

    Result:

    A new disabled rule using the naming convention Clone_<Rule name> is created. If a clone with that name already exists, PingOne automatically adds a numeric suffix. For example, Clone_<Rule name> (2).

  4. (Optional) Give the clone a unique, descriptive name to avoid confusion with the original.

  5. Review the settings of the cloned rule and verify copied mappings, filters, and connection references are what you expected.

  6. To enable the cloned rule, click the toggle to the right (blue).

    You can disable the cloned rule by clicking the toggle to the left (gray).

Next steps

After enabling a cloned rule, ensure you validate the resync and real-time sync behavior. Learn more in Viewing sync status.