> For the complete documentation index, see [llms.txt](https://newdocs.keeper.io/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://newdocs.keeper.io/en/keeperpam/privileged-access-manager/references/importing-pam-resources/validate-a-pam-project-import.md).

# Validate a PAM Project Import

Validate KeeperPAM project imports before creating resources.

Validate every generated PAM import before creating a project:

```bash
pam project import --filename /absolute/path/pam_import.json --name "My PAM Project" --dry-run
```

Use an absolute path. Confirm that Commander reports the expected resource and user counts before running the command without `--dry-run`.

## Machine connection requirements

For a usable `pamMachine`, provide both the management settings and the interactive connection settings:

| Setting                            | Purpose                                     | Example                        |
| ---------------------------------- | ------------------------------------------- | ------------------------------ |
| `port`                             | Management or rotation port                 | `22` for SSH, `5986` for WinRM |
| `operating_system`                 | Resource operating system                   | `Linux` or `Windows`           |
| `pam_settings.connection.protocol` | Interactive protocol                        | `ssh` or `rdp`                 |
| `pam_settings.connection.port`     | Interactive session port                    | `22` or `3389`                 |
| `administrative_credentials`       | PAM user used for administrative operations | Exact PAM user title or login  |
| `launch_credentials`               | PAM user used to launch the session         | Exact PAM user title or login  |

The machine `port` and connection `port` have different purposes. For example, a Windows machine can use WinRM on `5986` for management and RDP on `3389` for interactive sessions.

## Credential references

`administrative_credentials` and `launch_credentials` must reference a unique PAM user title or login. For a user owned by a PAM Directory, use the documented `Directory Title.User Title` format. For a local user nested under a machine, use the local user title or login.

Set `allow_supply_user` to `true` when a session user should be able to supply a username rather than selecting a launch credential.

## Rotation settings

Omit `rotation_settings` when rotation is not configured. Do not use an empty object. A complete rotation configuration includes a rotation type, enablement value, and schedule.

```json
"rotation_settings": {
  "rotation": "general",
  "enabled": "on",
  "schedule": {
    "type": "on-demand"
  }
}
```

If Commander reports `Failed to load rotation schedule` or stops at `0/N` resources, remove empty `rotation_settings` objects and rerun the dry run.

## Troubleshooting

| Symptom                                     | Check                                                                |
| ------------------------------------------- | -------------------------------------------------------------------- |
| No resources are parsed                     | Use an absolute `--filename` path and validate the JSON file.        |
| Fewer users than expected                   | Check for repeated usernames and titles in the CSV generator input.  |
| Missing machine port                        | Add the resource `port` and the protocol-specific connection `port`. |
| Missing administrator error during rotation | Verify the credential reference and remove empty rotation settings.  |

Replace all demonstration passwords and placeholders before any operational use.


---

# 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://newdocs.keeper.io/en/keeperpam/privileged-access-manager/references/importing-pam-resources/validate-a-pam-project-import.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.