Stay organized with collections
Save and categorize content based on your preferences.
Domain-wide delegation allows Google Workspace for Education super administrators to grant
third-party applications permission to access data of users within their domain
without requiring a specific user's consent. Domain-wide delegation is performed
in the Google Admin console by specifying the client ID of a service account
or third-party application.
A service account is an account that belongs to a Google Cloud project instead
of an individual user. Applications can request access to Google APIs on behalf
of the service account rather than on behalf of individual end-users. Service
accounts are set up in the Google Cloud console.
An OAuth client ID is a public identifier used to identify applications to
Google servers.
Domain-wide delegation set-up
A Google Workspace super administrator can set up the service account
or OAuth client ID with domain-wide delegation in the
Admin console.
In the Admin console, navigate to Main menumenu> Security > Access and data control > API Controls.
Under Domain wide delegation, select Manage Domain Wide Delegation.
Click Add new.
Enter the service account's client ID or the application's OAuth client ID
in the Client ID field. Enter the list of OAuth scopes that the service
account or application should be granted in the OAuth scopes field.
Click Authorize.
If an administrator installs an application for a domain from the
Google Workspace Marketplace, service accounts used by that application don't
need to be manually set-up. The required permissions are automatically provided
during installation.
[null,null,["Last updated 2025-08-28 UTC."],[],[],null,["# Domain-wide delegation allows Google Workspace for Education [super administrators](https://support.google.com/a/answer/2405986) to grant\nthird-party applications permission to access data of users within their domain\nwithout requiring a specific user's consent. Domain-wide delegation is performed\nin the Google Admin console by specifying the client ID of a service account\nor third-party application.\n| **Warning:** It's recommended that you avoid using domain-wide delegation if possible. If you do need to use domain-wide delegation, proceed with caution and read through the [best practices](https://support.google.com/a/answer/14437356).\n\nA **service account** is an account that belongs to a Google Cloud project instead\nof an individual user. Applications can request access to Google APIs on behalf\nof the service account rather than on behalf of individual end-users. Service\naccounts are set up in the Google Cloud console.\n\nAn **OAuth client ID** is a public identifier used to identify applications to\nGoogle servers.\n\nDomain-wide delegation set-up\n-----------------------------\n\nA Google Workspace super administrator can set up the service account\nor OAuth client ID with domain-wide delegation in the\nAdmin console.\n\n1. In the Admin console, navigate to **Main menu** menu **\\\u003e Security \\\u003e Access and data control \\\u003e API Controls**.\n2. Under **Domain wide delegation** , select **Manage Domain Wide Delegation**.\n3. Click **Add new**.\n4. Enter the service account's client ID or the application's OAuth client ID in the **Client ID** field. Enter the list of OAuth scopes that the service account or application should be granted in the **OAuth scopes** field.\n5. Click **Authorize**.\n\nIf an administrator installs an application for a domain from the\nGoogle Workspace Marketplace, service accounts used by that application don't\nneed to be manually set-up. The required permissions are automatically provided\nduring installation.\n\nResources\n---------\n\n- Domain-wide delegation [best practices](https://support.google.com/a/answer/14437356)"]]
