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

# License Installation

## Preferred Method

### Houdini ENV File 

The preferred method for installation is setting the PA\_LICENSE\_LOCATION environment variable.

Setting PA\_LICENSE\_LOCATION in your *houdini.env* file will look something like this:

`PA_LICENSE_LOCATION="D:/PA/2026-06-10_john-johnson_procedural-anatomy-commercial-license.json"`

[SideFX Docs - How to set environment variables](https://www.sidefx.com/docs/houdini/basics/config_env.html)

As a reminder:\
\- quote values that contain spaces.\
\- Set this before opening the toolset the first time.

## Legacy Method

<figure><img src="https://content.gitbook.com/content/czlF1HeE8ElPv7Dygz6P/blobs/46Eikw14n4Eu3j3cI7XD/01_02_dragAndDrop.gif" alt=""><figcaption><p>Opening a scene or creating a node will bring up the license install window.</p></figcaption></figure>

Upon placing a node in the Procedural Anatomy toolset a window will popup and you will be invited to drag & drop the license file into the window.

Once you drop the license file upon the window you will be able to access the toolset.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.procedural-anatomy.com/installation/license-installation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.