Access Context Manager: Node.js Client

release level npm version

accesscontextmanager client for Node.js

A comprehensive list of changes in each version may be found in the CHANGELOG.

Read more about the client libraries for Cloud APIs, including the older Google APIs Client Libraries, in Client Libraries Explained.

Table of contents:


Before you begin

  1. Select or create a Cloud Platform project.
  2. Enable billing for your project.
  3. Enable the Access Context Manager API.
  4. Set up authentication with a service account so you can access the API from your local workstation.

Installing the client library

npm install @google-cloud/access-context-manager

Using the client library

 * TODO(developer): Uncomment these variables before running the sample.
 *  Required. Resource name for the container to list AccessPolicy instances
 *  from.
 *  Format:
 *  `organizations/{org_id}`
// const parent = 'abc123'
 *  Number of AccessPolicy instances to include in the list. Default 100.
// const pageSize = 1234
 *  Next page token for the next batch of AccessPolicy instances. Defaults to
 *  the first page of results.
// const pageToken = 'abc123'

// Imports the Accesscontextmanager library
const {AccessContextManagerClient} =

// Instantiates a client
const accesscontextmanagerClient = new AccessContextManagerClient();

async function listAccessPolicies() {
  // Construct request
  const request = {

  // Run request
  const iterable = await accesscontextmanagerClient.listAccessPoliciesAsync(
  for await (const response of iterable) {



Samples are in the samples/ directory. Each sample's has instructions for running its sample.

SampleSource CodeTry it
Access_context_manager.commit_service_perimeterssource codeOpen in Cloud Shell
Access_context_manager.create_access_levelsource codeOpen in Cloud Shell
Access_context_manager.create_access_policysource codeOpen in Cloud Shell
Access_context_manager.create_gcp_user_access_bindingsource codeOpen in Cloud Shell
Access_context_manager.create_service_perimetersource codeOpen in Cloud Shell
Access_context_manager.delete_access_levelsource codeOpen in Cloud Shell
Access_context_manager.delete_access_policysource codeOpen in Cloud Shell
Access_context_manager.delete_gcp_user_access_bindingsource codeOpen in Cloud Shell
Access_context_manager.delete_service_perimetersource codeOpen in Cloud Shell
Access_context_manager.get_access_levelsource codeOpen in Cloud Shell
Access_context_manager.get_access_policysource codeOpen in Cloud Shell
Access_context_manager.get_gcp_user_access_bindingsource codeOpen in Cloud Shell
Access_context_manager.get_iam_policysource codeOpen in Cloud Shell
Access_context_manager.get_service_perimetersource codeOpen in Cloud Shell
Access_context_manager.list_access_levelssource codeOpen in Cloud Shell
Access_context_manager.list_access_policiessource codeOpen in Cloud Shell
Access_context_manager.list_gcp_user_access_bindingssource codeOpen in Cloud Shell
Access_context_manager.list_service_perimeterssource codeOpen in Cloud Shell
Access_context_manager.replace_access_levelssource codeOpen in Cloud Shell
Access_context_manager.replace_service_perimeterssource codeOpen in Cloud Shell
Access_context_manager.set_iam_policysource codeOpen in Cloud Shell
Access_context_manager.test_iam_permissionssource codeOpen in Cloud Shell
Access_context_manager.update_access_levelsource codeOpen in Cloud Shell
Access_context_manager.update_access_policysource codeOpen in Cloud Shell
Access_context_manager.update_gcp_user_access_bindingsource codeOpen in Cloud Shell
Access_context_manager.update_service_perimetersource codeOpen in Cloud Shell
Quickstartsource codeOpen in Cloud Shell
Quickstartsource codeOpen in Cloud Shell

The Access Context Manager Node.js Client API Reference documentation also contains samples.

Supported Node.js Versions

Our client libraries follow the Node.js release schedule. Libraries are compatible with all current active and maintenance versions of Node.js. If you are using an end-of-life version of Node.js, we recommend that you update as soon as possible to an actively supported LTS version.

Google's client libraries support legacy versions of Node.js runtimes on a best-efforts basis with the following warnings:

  • Legacy versions are not tested in continuous integration.
  • Some security patches and features cannot be backported.
  • Dependencies cannot be kept up-to-date.

Client libraries targeting some end-of-life versions of Node.js are available, and can be installed through npm dist-tags. The dist-tags follow the naming convention legacy-(version). For example, npm install @google-cloud/access-context-manager@legacy-8 installs client libraries for versions compatible with Node.js 8.


This library follows Semantic Versioning.

This library is considered to be stable. The code surface will not change in backwards-incompatible ways unless absolutely necessary (e.g. because of critical security issues) or with an extensive deprecation period. Issues and requests against stable libraries are addressed with the highest priority.

More Information: Google Cloud Platform Launch Stages


Contributions welcome! See the Contributing Guide.

Please note that this, the samples/, and a variety of configuration files in this repository (including .nycrc and tsconfig.json) are generated from a central template. To edit one of these files, make an edit to its templates in directory.


Apache Version 2.0