> For the complete documentation index, see [llms.txt](https://documentation.grax.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.grax.com/reuse-data/managed-package/second-generation/uninstall.md).

# Uninstall

{% hint style="danger" %}

#### User Impact

Before uninstalling any Managed Package, always make sure that your business and users are not actively depending on it. Uninstalling a package requires removing all components, custom code, and custom objects associated with that package. Proceed at your own risk.
{% endhint %}

If it becomes necessary to remove the second-generation Managed Package from your Salesforce org, manual effort may be required. Due to the customization that happens after a package is installed (like adding components to page layouts), it's almost always more difficult to unwind and uninstall a package than add one.

The steps below walk through the process of uninstalling this package. If you become stuck or encounter unexpected issues while following these steps, feel free to [contact our Support team](/support/get-support.md) for assistance.

{% stepper %}
{% step %}

### Log in to Salesforce

Log in to your Salesforce org via your standard login process as a user with the permissions to uninstall Managed Packages. The standard "System Admin" profile is sufficient.
{% endstep %}

{% step %}

### Try Uninstalling the Package

Open the "Setup" menu, then open "Installed Packages" via the Quickfind search.

<figure><img src="/files/ULyelRJ91OAjxbk0HING" alt=""><figcaption></figcaption></figure>

Find "GRAX Lightning Web Components" in the packages list, and click "Uninstall."

<figure><img src="/files/gufpihZZaNRqKpGhMkpQ" alt=""><figcaption></figcaption></figure>

Check the confirmation checkbox on the next page, and click "Uninstall."

<figure><img src="/files/qJ3Chu80ilXfayRsbLtU" alt=""><figcaption></figcaption></figure>

If the uninstall is successful, you will receive a confirmation email. If you receive this email, you are done with this guide and do not need to continue reading. If your uninstall failed, keep reading.

<figure><img src="/files/GLcvjZN75veEUFjps3Rf" alt=""><figcaption></figcaption></figure>

On the first attempt, it is likely that you will receive errors about components or other resources in the package still being used somewhere. Usually, these just mean that you have page layouts that still contain the component. The error page should list the page layouts and resources impacted.

<figure><img src="/files/zPjxnwjCFvZPYQwUTPZ8" alt=""><figcaption></figcaption></figure>

It is your responsibility to update these page layouts to no longer include the GRAX components (or otherwise resolve any errors during installation). Do your best to resolve all possible issues, then continue.
{% endstep %}

{% step %}

### Try Uninstalling the Package Again

Now that you've resolved all possible issues that appeared during the previous attempt, try uninstalling the package again using the original steps.

If you encounter more issues, resolve them and repeat this process until the uninstall is successful. If you come across a reported issue that you cannot resolve, feel free to [reach out to our Support team](/support/get-support.md) for assistance.
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.grax.com/reuse-data/managed-package/second-generation/uninstall.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.