> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://rockwell.ferndocs.com/best-practices/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://rockwell.ferndocs.com/_mcp/server.

# Best Practices

## Docs

- [Best Practices for Using API Keys](https://rockwell.ferndocs.com/best-practices/best-practices-for-using-api-keys.md): General guidelines for managing and using API keys safely
- [Restrict API Keys](https://rockwell.ferndocs.com/best-practices/restrict-api-keys.md): Limit API key permissions to only what is needed
- [Restrict Developer Portal Account Access](https://rockwell.ferndocs.com/best-practices/restrict-developer-portal-account-access.md): Control who can access your developer portal account
- [Regularly Audit Your API Keys](https://rockwell.ferndocs.com/best-practices/regularly-audit-your-api-keys.md): Review and clean up unused or stale API keys
- [Use Independent API Keys for Different Apps](https://rockwell.ferndocs.com/best-practices/use-independent-api-keys-for-different-apps.md): Isolate credentials across applications
- [Regenerate API Keys Regularly](https://rockwell.ferndocs.com/best-practices/regenerate-api-keys-regularly.md): Rotate keys on a regular schedule to reduce risk
- [Create a Generic IAM ID for Developer Portal Access](https://rockwell.ferndocs.com/best-practices/create-a-generic-iam-id-for-developer-portal-access.md): Use a shared IAM identity for portal access management
- [Store API Keys in a Secure Location](https://rockwell.ferndocs.com/best-practices/store-api-keys-in-a-secure-location.md): Keep credentials in secret managers or vaults
- [Encrypt Keys on Code Repositories](https://rockwell.ferndocs.com/best-practices/encrypt-keys-on-code-repositories.md): Never commit plaintext keys to version control


> **Note:** This page contains both a page directory (above) and the landing page content (below). The page directory is generated for agent use and does not appear on the landing page.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://rockwell.ferndocs.com/best-practices/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://rockwell.ferndocs.com/_mcp/server.

# Best Practices

Follow these best practices to keep your Plex API integrations secure, reliable, and maintainable.

## What's covered

* [**Best Practices for Using API Keys**](/best-practices/best-practices-for-using-api-keys) — General guidelines for managing and using API keys safely
* [**Restrict API Keys**](/best-practices/restrict-api-keys) — Limit API key permissions to only what is needed
* [**Restrict Developer Portal Account Access**](/best-practices/restrict-developer-portal-account-access) — Control who can access your developer portal account
* [**Regularly Audit Your API Keys**](/best-practices/regularly-audit-your-api-keys) — Review and clean up unused or stale API keys
* [**Use Independent API Keys for Different Apps**](/best-practices/use-independent-api-keys-for-different-apps) — Isolate credentials across applications
* [**Regenerate API Keys Regularly**](/best-practices/regenerate-api-keys-regularly) — Rotate keys on a regular schedule to reduce risk
* [**Create a Generic IAM ID for Developer Portal Access**](/best-practices/create-a-generic-iam-id-for-developer-portal-access) — Use a shared IAM identity for portal access management
* [**Store API Keys in a Secure Location**](/best-practices/store-api-keys-in-a-secure-location) — Keep credentials in secret managers or vaults
* [**Encrypt Keys on Code Repositories**](/best-practices/encrypt-keys-on-code-repositories) — Never commit plaintext keys to version control