---
schema_version: "1"
id: c48aeb2ab80eb9ab45109cca51cf386b8df02b33456d5d737903beef014b6c38
title: Package Installation Key for Second-Generation Managed Packages
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/platform-pkg-exchange/managed_packaging/guides/second-generation/sfdx-dev-dev2gp-config-installkey.md
canonical_url: https://developer.salesforce.com/docs/platform/pkg2-dev/guide/sfdx-dev-dev2gp-config-installkey.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 209b1bf220c63c0f411a44283caa647f76f82cba1123b27fcdd3b54da4000a8b
products:
  - Second-Generation Managed Packaging Developer Guide
  - merged-docs
---

# Package Installation Key for Second-Generation Managed Packages

To ensure the security of the metadata in your second-generation managed package, you must specify an installation key when creating a package version. Package creators provide the key to authorized subscribers so they can install the package. Package installers provide the key during installation, whether installing the package from the CLI or from a browser. An installation key is the first step during installation. The key ensures that no package information, such as the name or components, is disclosed until the correct installation key is supplied.

To set the installation key, add the `--installation-key` parameter to the command when you create the package version. This command creates a package and protects it with the installation key.

```nolang
sf package version create --package "Expense Manager" --installation-key "JSB7s8vXU93fI"
```

Supply the installation key when you install the package version in the target org.

```nolang
sf package install --package "Expense Manager" --installation-key "JSB7s8vXU93fI”
```

## Change the Installation Key for an Existing Package Version

You can change the installation key for an existing package version with the `sf package version update` command.

```nolang
sf package version update --package "Expense Manager@1.2.0-4" --installation-key “HIF83kS8kS7C”
```

## Create a Package Version Without an Installation Key

If you don’t require security measures to protect your package metadata, you can create a package version without an installation key.

```nolang
sf package version create --package "Expense Manager" --installation-key-bypass
```

## Check Whether a Package Version Requires an Installation Key

To determine whether a package version requires an installation key, use the `sf package version list` CLI command.