# Deleting Aura Components from Managed Packages

After you’ve released a managed package, you may decide to refactor the package and delete an Aura component. It’s your responsibility to educate your customers about the potential impact from any components you delete. In the Release Notes for your upgraded package, list all custom components you’ve deleted and notify customers of any necessary actions.

:::note
To enable component deletion in your packaging org, log a case in the [Partner Community](https://partners.salesforce.com/).
:::

To delete an Aura component from a managed package:

1. From Setup, enter `Lightning Components` in the Quick Find box.
2. Select **Lightning Components**.
3. Click **Del** for the component that you want to delete.

   ![Lightning Components in Setup](https://a.sfdcstatic.com/developer-website/sfdocs/platform/media/aura-platform/apps_packaging_delete_component.png)

You can delete an Aura component from the Developer Console also.

:::note
When a developer removes an Aura component from a package, the component remains in a subscriber’s org after they install the upgraded package. The administrator of the subscriber’s org can delete the component, if desired. This behavior is the same for an Aura component with a `public` or `global` access value.
:::

The `access` attribute on the `aura:component` tag can be set to `public` or `global` to control whether the component can be used outside of the component’s namespace.

We recommend a two-stage process to package developers when you delete an Aura component with `global` access. This process ensures that a global component that you delete from the package has no dependencies on the other items in the package.

1. Stage one: Remove references

   1. Edit the global component that you want to delete to remove all references to other Lightning components.
   2. Upload your new package version.
   3. Push the stage-one upgrade to your subscribers.

2. Stage two: Delete your obsolete component

   1. Delete the global Lightning component from the package.
   2. Optionally, delete other related components and classes.
   3. Upload your new package version.
   4. Push the stage-two upgrade to your subscribers.

**See Also**

- [Component Access Control](/docs/platform/aura-platform/guide/access-components.md)
- [*Second-Generation Managed Packaging Developer Guide*: Remove Metadata Components from Second-Generation Managed Packages](https://developer.salesforce.com/docs/atlas.en-us.pkg2\_dev.meta/pkg2\_dev/sfdx_dev_dev2gp_remove_md_components.htm)
- [*First-Generation Managed Packaging Developer Guide*: Delete Components from First-Generation Managed Packages](https://developer.salesforce.com/docs/atlas.en-us.pkg1\_dev.meta/pkg1\_dev/packaging_managed_component_deletion.htm)