We’ve updated the wording for key software enforcement actions in the Application Management installations experience so it better matches how SecureHive actually works and reduces confusion for admins.

What’s changed

• “Install” → “Enforce Install”

  • On the Application Details page, the primary install action is now labeled Enforce Install.

  • The Install Software (All Devices) modal copy (title, body, primary button) now consistently uses Enforce Install language.

• “Uninstall” → “Enforce Removal”

  • On the Uninstall Application flow, the primary uninstall action is now Enforce Removal.

  • The Enforce Removal confirmation modal now:

    • Uses a clear question in the title:
      Remove this app from the device?

    • Clarifies what happens next:
      This application will be uninstalled and moved to the blocklist for this device. If the user reinstalls it, it will be automatically removed until you remove it from the blocklist.

    • Uses Enforce Removal on the primary button.

  • The toast notification after enforcing removal also uses the new Enforce Removal terminology.

• “Disable Force Installation” → “Clear Enforcement”

  • Anywhere you previously saw Disable Force Installation (for devices with a forced install), the action is now labeled Clear Enforcement.

  • The Clear Enforcement confirmation modal and its toast message both use Clear Enforcement consistently.

Behavior (what stays the same)

• Under the hood, all actions behave exactly as before:

  • Enforce Install still enforces installation.

  • Enforce Removal still uninstalls and moves the app to the blocklist for the device.

  • Clear Enforcement still removes the enforced state for that device/app.

• Button placement, hierarchy (primary/secondary/tertiary), and toast behavior are unchanged; only the wording and supporting copy were updated.