---
schema_version: "1"
id: ec5963cd90556dd92e6b52ca44fc8343488998a393f452199fe022240b1512d4
title: Editable Properties After Package Promotion or Installation
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/platform-pkg-exchange/managed_packaging/guides/metadata-components/mdc-editable-property-definitions.md
canonical_url: https://developer.salesforce.com/docs/platform/pkg2-dev/guide/mdc-editable-property-definitions.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 21e499d7dd29f6c66eae9bf209a5a4b7a922a2e782d357aef4916edcb3339976
products:
  - Second-Generation Managed Packaging Developer Guide
  - merged-docs
---

# Editable Properties After Package Promotion or Installation

Certain properties on metadata components are editable after the managed package is installed.

**Only Package Developer Can Edit:** The package developer can edit specific component properties. These properties are locked in the subscriber’s org. During package upgrade, the changes made by the package developer are applied in the subscriber org. For example, when you update the code in an Apex class or the custom permissions in a permission set, subscribers receive those updates during their package upgrade.

**Both Subscriber and Package Developer Can Edit:** Both the subscriber and package developer can edit these component properties, but developer changes are only applied to new subscriber installs. This approach prevents a package upgrade from overwriting changes made by the subscriber. For example, the help text on a custom field, and the page layout of a custom object are editable by both the subscriber and package developer. The subscriber can modify the page layout or help text, and trust that their changes won’t be overwritten by a future package upgrade.

**Neither Subscriber or Package Developer Can Edit:** After a package is promoted and released, these component properties are locked and can’t be edited by the package developer or the subscriber. For example, the API names of packaged components are locked and can’t be edited after the package version is promoted and released.