> For the complete documentation index, see [llms.txt](https://doc.sitecorepowershell.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.sitecorepowershell.com/modules.md).

# Modules

Sitecore PowerShell Extensions provides an organization structure composed of *modules*, *libraries*, and *scripts*. Modules make up the highest level and can be grouped together by module folders.

Some benefits to using modules:

* The [integration points](/modules/integration-points.md) contained within each module can be enabled or disabled globally. For this to take full affect the integration should be rebuilt in the ISE.
* Organization of custom scripts is a cinch.
* More reasons can be found in Adam's [post](https://github.com/SitecorePowerShell/Book/tree/9c7126d7a38df6ef372e8baef52f9a02baabd550/modules/\[https:/blog.najmanowicz.com/2014/11/01/sitecore-powershell-extensions-3-0-modules-proposal/]/README.md).

{% hint style="warning" %}
The *Platform* module is one you should avoid changing.
{% endhint %}

## Create a custom module

Getting started with your own module is a short process and something you should do for all of your custom scripts.

1. Navigate to the *Script Library* item and *Insert -> PowerShell Script Module*.

   ![New Module](/files/-LA37dVXhhj8uPEGxIb4)
2. Enter the name for the new module and click *OK*.
3. Right click the new module and *Scripts -> Create libraries for integration points*.

   ![Integration Points](/files/-LA37_A5p7JMnQmXDmd1)
4. Select the appropriate integration points for your module.

   ![Integration Point Libraries](/files/-LA37_BdW8tzCH7IRNSP)
5. Select the module and enable for use.

   ![Module Activation](/files/-LA37dYPeRyhdRVg4rOM)
6. Open the ISE, switch to the *Settings* tab, and rebuild integrations.