---
schema_version: "1"
id: 84058893c06cc59a7dfdfb41d45ef80b0f12d6bb9bf4a3ec1bdd0dc49b6007cd
title: Manage Package Upgrades with Customized Push Upgrades
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/260-0-0/rn_packaging_customized_push_upgrades.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_packaging_customized_push_upgrades.htm&release=260&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: eb56948e032d4b9d65678ccea8b3a6b22cebff115db50aae7afc3e7352ff57a1
description: Customized push upgrades enable partners and customers to manage the push upgrade lifecycle. With this feature, partners can grant select customers the ability to block push upgrades. Customized push upgrades are especially useful for highly regulated environments where strict compliance and validation protocols require control of upgrade timing and version oversight. This feature provides the granular control necessary to ensure compliance and system stability during version transitions.
products:
  - Cross Cloud Packages Solutions
release: "260"
---
# Manage Package Upgrades with Customized Push Upgrades

Customized push upgrades enable partners and customers to manage the push upgrade lifecycle. With this feature, partners can grant select customers the ability to block push upgrades. Customized push upgrades are especially useful for highly regulated environments where strict compliance and validation protocols require control of upgrade timing and version oversight. This feature provides the granular control necessary to ensure compliance and system stability during version transitions.

**Where:** This change applies to second- and first-generation managed packages.

**Who:** To manage customized push upgrades, users need the permissions to perform packaging push upgrades.

**Why:** In highly regulated industries like healthcare or finance, an unannounced automated upgrade can disrupt validated workflows or trigger compliance audits. Customized push upgrades allow you to test new package versions in a sandbox environment before scheduling the production push at a time that minimizes operational risk.

#### See Also

- [_Second-Generation Managed Packaging Developer Guide_: Enable a Package Subscriber to Restrict Push Upgrades](https://developer.salesforce.com/docs/atlas.en-us.pkg2_dev.meta/pkg2_dev/push_upgrade_customized.htm)
- [_Second-Generation Managed Packaging Developer Guide_: Push a Package Upgrade for Second-Generation Managed Packages](https://developer.salesforce.com/docs/atlas.en-us.pkg2_dev.meta/pkg2_dev/push_upgrade_intro_2GP.htm)
- [_First-Generation Managed Packaging Developer Guide_: Enable a Package Subscriber to Restrict Push Upgrades](https://developer.salesforce.com/docs/atlas.en-us.pkg1_dev.meta/pkg1_dev/push_upgrade_customized.htm)
- [_First-Generation Managed Packaging Developer Guide_: Push Package Upgrades to Subscribers](https://developer.salesforce.com/docs/atlas.en-us.pkg1_dev.meta/pkg1_dev/push_upgrade_intro.htm)