# Project access

> **Related:** [Hand the website over to your client](https://docs.atmyapp.com/ai-assistant.md) · [Changelog](https://docs.atmyapp.com/changelog.md) · [Deploy your website](https://docs.atmyapp.com/deployment.md) · [Examples](https://docs.atmyapp.com/examples.md) · [Choose your integration](https://docs.atmyapp.com/integrations.md) · [Connect a JavaScript website](https://docs.atmyapp.com/quick-start.md) · [Troubleshooting](https://docs.atmyapp.com/troubleshooting.md)
> **Also:** [HTML version](https://docs.atmyapp.com/account) · [Docs index](https://docs.atmyapp.com/llms.txt)

---
Use a public website API key for the runtime SDK. Use a CLI token to connect the local workspace for administrative operations such as schema migration. They are different credentials with different purposes.

Keep `.ama/session.json` out of source control. Keep CLI tokens in protected local or CI configuration. Confirm the target project before uploading schema or content changes. Preview keys belong to the specific preview, not permanent production configuration.

For project access and billing details, use your AtMyApp account or contact [contact@atmyapp.com](mailto:contact@atmyapp.com). These SDK docs do not define account plan limits or promise particular permissions.