> Index of every Falcon docs page, for assistants: https://falcon.com/docs/llms.txt

# Add the sub-company's own key

A sub-company can add its own model key on Your keys. That key is used instead of the parent company's key for the same provider. The parent never sees it.

This is allowed even when **Sub-companies can change models** is off.

## Add key

- Open the sub-company. Go to **Connections › Model providers › Your keys**.
- A provider with no key says **No key yet**. Choose **Add key**.
- The key is write-only: nobody can read it back. Falcon tests it when you save it. A key the provider refuses shows as **Key not working**.
- The section says: **Connect your own account with a model provider. The provider bills you directly, and the usage still shows in your reports and limits.**

## The sub-company's key wins

- For that provider, calls use the sub-company's key, not the parent's. **Runs through** names it as this company's own key.
- The parent company's other keys are still used for providers where this company has **No key yet**.
- The parent cannot see, replace or remove the sub-company's key. Removing the parent's key does not remove this one.
- While the company is still a sub-company, that usage still counts on both companies' spending limits and is billed to the parent. See [How a sub-company's usage is billed](https://falcon.com/docs/sub-company-billing).

## Related

- [Use the parent company's models](https://falcon.com/docs/sub-company-models)
- [How a sub-company's usage is billed](https://falcon.com/docs/sub-company-billing)
- [Detach a sub-company](https://falcon.com/docs/detach-a-sub-company)