feat(admin): Add admin controls documentation

[skeshive]

Linked Issues

https://github.com/google-gemini/maintainers-gemini-cli/issues/1185

[gemini-code-assist]

Summary of Changes

Hello @skeshive, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces comprehensive documentation for enterprise-level administrative controls within the Gemini CLI. It outlines various security policies and configuration settings that administrators can enforce globally, ensuring a consistent security posture across an organization. The documentation details how these controls override local user settings and provides in-depth information on specific features like Strict Mode, Extensions, MCP server management, and Unmanaged Capabilities, including detailed client enforcement logic for MCP server allowlists.

Highlights

• New Documentation for Enterprise Admin Controls: A new documentation page, 'Enterprise Admin Controls', has been added to detail how administrators can manage and enforce security policies and configuration settings across their organization within the Gemini CLI.
• Detailed Control Explanations: The documentation provides in-depth explanations for various admin controls, including 'Strict Mode', 'Extensions', 'MCP' (with sub-sections for enabling/disabling and MCP Servers allowlisting), and 'Unmanaged Capabilities'.
• MCP Server Allowlist and Enforcement Logic: The 'MCP Servers' section includes a detailed JSON format for defining an explicit allowlist of trusted MCP servers, along with comprehensive client enforcement logic explaining how the allowlist interacts with user's local configurations, including configuration merging and field overriding rules.
• Distinction Between Admin Controls and System Settings: The document clarifies the difference between immutable admin controls and user-modifiable system-wide settings, emphasizing that admin controls are the preferred method for policy enforcement.
• Sidebar Navigation Update: The docs/sidebar.json file has been updated to include a new entry for 'Enterprise admin controls', making the new documentation accessible through the navigation.

Changelog

• docs/admin/enterprise-controls.md
  • Added a new documentation file detailing enterprise admin controls.
  • Included sections for Strict Mode, Extensions, MCP (Enabled/Disabled and Servers allowlist), and Unmanaged Capabilities.
  • Provided a JSON format example for MCP server allowlists and explained client enforcement logic for configuration merging.
• docs/sidebar.json
  • Added a new entry for 'Enterprise admin controls' to the documentation sidebar, linking to the newly created docs/admin/enterprise-controls.md.

Activity

• The pull request was created by skeshive.
• No further activity has been recorded yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-cli]

Hi @skeshive, thank you so much for your contribution to Gemini CLI! We really appreciate the time and effort you've put into this.

We're making some updates to our contribution process to improve how we track and review changes. Please take a moment to review our recent discussion post: Improving Our Contribution Process & Introducing New Guidelines.

Key Update: Starting January 26, 2026, the Gemini CLI project will require all pull requests to be associated with an existing issue. Any pull requests not linked to an issue by that date will be automatically closed.

Thank you for your understanding and for being a part of our community!

[gemini-code-assist]

Code Review

This pull request adds valuable documentation for the Enterprise Admin Controls. The new page clearly explains the available controls and their enforcement logic. I've found one high-severity issue where the documentation for tool filtering in MCP server allowlists is inconsistent with the likely implementation, which could lead to security misconfigurations. I've provided a suggestion to correct the documentation.

[chrstnb]

Build failed: Build process failed with link errors:

21:06:56 [ERROR] ✗ Found 1 invalid link in 1 file.
21:06:56   └─ /docs/tools/extensions - invalid link
21:06:56 [ERROR] [starlight-links-validator-integration] An unhandled error occurred while running the "astro:build:done" hook

[github-actions]

Size Change: -2 B (0%)

Total Size: 24.3 MB

ℹ️ View Unchanged

Filename	Size	Change
./bundle/gemini.js	24.3 MB	-2 B (0%)
./bundle/sandbox-macos-permissive-closed.sb	1.03 kB	0 B
./bundle/sandbox-macos-permissive-open.sb	890 B	0 B
./bundle/sandbox-macos-permissive-proxied.sb	1.31 kB	0 B
./bundle/sandbox-macos-restrictive-closed.sb	3.29 kB	0 B
./bundle/sandbox-macos-restrictive-open.sb	3.36 kB	0 B
./bundle/sandbox-macos-restrictive-proxied.sb	3.56 kB	0 B

_{compressed-size-action}

[chrstnb]

Build failed: Build process failed with link errors:

15:15:03 [ERROR] ✗ Found 1 invalid link in 1 file.
15:15:03   └─ /docs/tools/extensions - invalid link
15:15:03 [ERROR] [starlight-links-validator-integration] An unhandled error occurred while running the "astro:build:done" hook