summaryrefslogtreecommitdiff
path: root/docs/cli/configuration.md
diff options
context:
space:
mode:
authorchristine betts <[email protected]>2025-08-20 17:04:03 +0000
committerGitHub <[email protected]>2025-08-20 17:04:03 +0000
commit99b1ba9d1032768dc8826ee713f51a9812f9c889 (patch)
tree5ea923137b430de671e013d5c14b4cd0b97c46ad /docs/cli/configuration.md
parent0e2480580648788f824a6fd7f76ad452bb6cf771 (diff)
Add enterprise settings docs (#6076)
Diffstat (limited to 'docs/cli/configuration.md')
-rw-r--r--docs/cli/configuration.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/docs/cli/configuration.md b/docs/cli/configuration.md
index 24b3017a..fd6f69f0 100644
--- a/docs/cli/configuration.md
+++ b/docs/cli/configuration.md
@@ -29,6 +29,8 @@ Gemini CLI uses `settings.json` files for persistent configuration. There are th
**Note on environment variables in settings:** String values within your `settings.json` files can reference environment variables using either `$VAR_NAME` or `${VAR_NAME}` syntax. These variables will be automatically resolved when the settings are loaded. For example, if you have an environment variable `MY_API_TOKEN`, you could use it in `settings.json` like this: `"apiKey": "$MY_API_TOKEN"`.
+> **Note for Enterprise Users:** For guidance on deploying and managing Gemini CLI in a corporate environment, please see the [Enterprise Configuration](./enterprise.md) documentation.
+
### The `.gemini` directory in your project
In addition to a project settings file, a project's `.gemini` directory can contain other project-specific files related to Gemini CLI's operation, such as: