Google Antigravity Gemini Enterprise Setup Guide
On this page
Quick answer
Before enabling Antigravity, verify an eligible Gemini Enterprise edition and a project linked to an invoiced Cloud Billing account. Google documents separate roles: Gemini Enterprise Admin configures AI developer tools and views metrics, while Gemini Enterprise User is required to access them. The Admin role alone does not grant user access.
Setup sequence
- Confirm the subscription edition, project, invoiced billing account, active invoice, and current account notification requirements.
- Assign the narrowest admin role for configuration and the User role only to approved pilot participants.
- Enable AI developer tools and select Antigravity surfaces and models deliberately.
- Configure workspace sandboxing, file and terminal controls, browser and MCP access, audit logging, and any custom roles.
- Record standard quota, pooled usage, overage state, project budget or caps, alerts, metrics, and cost owner.
- Pilot one reversible repository with no production credentials and preserve normal review and deployment protections.
Required evidence
Capture screenshots or exported configuration for roles, settings, model routing, global endpoint warnings, audit logs, budget and overage controls, and the extension or CLI versions. Recheck access with an unauthorized user; do not infer denial from the intended configuration.
Run tests for wrong role, wrong project, blocked file, terminal denial, unapproved browser or MCP destination, model unavailability, quota exhaustion, overage stop, audit visibility, user revocation, and rollback.
Choose a surface with the 2.0 vs CLI vs IDE comparison and complete the enterprise readiness checklist.
Official sources
Source check: August 23, 2026. Verify current editions, billing, notices, roles, settings, models, Regions, quotas, and rollout availability.