# How to create a PowerPack

> Create a PowerPack from Applications and Packages in the root point of your installation.

Source: https://docs.capaone.com/capainstaller/the-capainstaller-console/configuration-management/how-to-use-configuration-management/working-with-powerpacks/how-to-create-a-powerpack/  
Product: CapaInstaller — a separate CapaSystems product; do not apply this page to any other.

Creating a PowerPack is straightforward, as it starts by right-clicking Applications and Packages in the root point of your installation and then clicking on Create PowerPack…

![](/attachments/capainstaller/6a06f038-6950-4fd3-a2c8-bca537765ae6.png)

Fill in the Package Name and set a Package Version and a Description optionally. The Display name automatically follows a concatenation of name and version. You can edit the Display Name manually if you want to. When you’re done, click Create.

![](/attachments/capainstaller/a70d91b0-a691-4c62-94a9-33c112f99646.png)

The newly created PowerPack is then visible inside the CI Console. In the same way that CapaPacks differ from native packs by the blue color, PowerPacks are shown with a green package icon.

![](/attachments/capainstaller/3f7fb0bf-727b-4db2-9ffc-362ff057f1de.png)

### The package folder

Right-click the PowerPack and choose **Open folder in Windows Explorer** to see its files on disk. A PowerPack folder contains three subfolders:

| Folder | Contents |
|---|---|
| `Kit` | The files the package needs at install/uninstall time (installers, configs, etc.) — reference them from your script via `$global:Packageroot\kit\...`. Whenever you add or change a file here, right-click the package and choose **Rebuild CapaInstaller.kit** so the change is picked up. |
| `Scripts` | Always empty — the install/uninstall scripts themselves live in the SQL database, not on disk. See [Editing installation scripts](/capainstaller/the-capainstaller-console/configuration-management/how-to-use-configuration-management/working-with-powerpacks/editing-installation-scripts/). |
| `Zip` | The built `CapaInstaller.kit` — this is what actually gets downloaded to clients and unzipped to reconstruct the `Kit` folder contents. It's regenerated whenever you rebuild the kit. |