Stay organized with collections
Save and categorize content based on your preferences.
This document describes methods to help prevent usage of
Gemini Code Assist licenses across an organization, and scenarios
where you might want to limit that usage.
By design, Gemini Code Assist licenses are assigned to individual
users, not organizations or projects. This design lets individual users use
Gemini Code Assist across multiple organizations.
However, some large organizations, such as global system integrators (GSIs),
might want to
prevent cross-organization usage.
For example:
Developers working on projects that have different billing accounts. For
instance, you might let a developer work on one project but limit access to
other projects because they have different billing accounts, even if they are
in the same organization.
Developers working on multiple projects from different customers. For
instance, a developer might work on projects for delivery organizations that
have different tenancies and tools.
Methods to help prevent cross-organization usage
To help prevent cross-organization usage of Gemini Code Assist in
a project, you can do one of the following:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[[["\u003cp\u003eGemini Code Assist licenses are assigned to individual users, allowing them to use the service across multiple organizations.\u003c/p\u003e\n"],["\u003cp\u003eLarge organizations may need to prevent cross-organization usage of Gemini Code Assist for developers working on projects with different billing accounts or different customers.\u003c/p\u003e\n"],["\u003cp\u003eCross-organization usage of Gemini Code Assist can be prevented by either disabling the Gemini for Google Cloud API on a project or by using Identity and Access Management (IAM) denial policies to deny user access.\u003c/p\u003e\n"]]],[],null,["# Help prevent cross-organization license usage\n\nThis document describes methods to help prevent usage of Gemini Code Assist licenses across an organization, and scenarios where you might want to limit that usage.\n\n\u003cbr /\u003e\n\nBy design, Gemini Code Assist licenses are assigned to individual\nusers, not organizations or projects. This design lets individual users use\nGemini Code Assist across multiple organizations.\n\nHowever, some large organizations, such as global system integrators (GSIs),\nmight want to\n[prevent cross-organization usage](#methods_to_help_prevent_cross-organization_usage).\nFor example:\n\n- **Developers working on projects that have different billing accounts.** For instance, you might let a developer work on one project but limit access to other projects because they have different billing accounts, even if they are in the same organization.\n- **Developers working on multiple projects from different customers.** For instance, a developer might work on projects for delivery organizations that have different tenancies and tools.\n\nMethods to help prevent cross-organization usage\n------------------------------------------------\n\nTo help prevent cross-organization usage of Gemini Code Assist in\na project, you can do one of the following:\n\n- [Disable the Gemini for Google Cloud API on a project](/gemini/docs/turn-off-gemini#companion-api).\n- Use Identity and Access Management (IAM) [denial policies](/iam/docs/deny-overview) to deny user access to the project."]]
