Skip to main content
command

gws-cloudidentity — Claude Code command to run Cloud Identity admin tasks

A slash command that sends Google Cloud Identity calls through the gws CLI: groups, memberships, devices, SSO profiles. Useful when admin work starts in the chat.

Install into Claude Code · claude-code-templates All methods and platforms ↓
npx claude-code-templates@latest --command google-workspace/gws-cloudidentity
Open on GitHub

What gws-cloudidentity does

Under the hood the command expands to gws cloudidentity <resource> <method> [flags] and runs it with your credentials. The surface covers groups (create, delete, search, security settings), group memberships, devices including wipe and cancelWipe, OIDC and SAML SSO profiles, SSO assignments, and policies. The full resource list comes from gws cloudidentity --help.

Before touching the API it checks gws --version and gws auth status, then pulls the method schema with gws schema cloudidentity.<resource>.<method>; that schema drives the --params and --json flags. Pagination goes through --max-results and --page-token, and the command walks you through API errors and quota limits.

No installed gws and no working auth means nothing runs, so gws auth status has to report a live session. Device creation is limited to Enterprise Standard, Enterprise Plus, Enterprise for Education or Cloud Identity Premium licenses. The referenced ../gws-shared/SKILL.md must exist; the command suggests gws generate-skills when it is absent.

What it helps with

  • create a group and add members to it
  • look up a group by entity key
  • wipe a company-owned device remotely
  • cancel a pending device wipe
  • list SAML or OIDC profiles before configuring SSO

Example prompts for the agent

  • gws-cloudidentity groups list --params '{"parent":"customers/my_customer"}'
  • Use gws-cloudidentity to create a devops group and add two members
  • gws-cloudidentity devices wipe --params '{"name":"devices/123"}'

How to install gws-cloudidentity

1claude-code-templates

npx claude-code-templates@latest --command google-workspace/gws-cloudidentity

2Manually: put the files in place

.claude/commands/gws-cloudidentity.md

Call it with /gws-cloudidentity. For all projects use ~/.claude/commands/

Questions about gws-cloudidentity

How do I install gws-cloudidentity in Claude Code?

Run npx claude-code-templates@latest --command google-workspace/gws-cloudidentity; the command lands at .claude/commands/gws-cloudidentity.md.

What does gws-cloudidentity do?

It wraps the Google Workspace CLI and issues Cloud Identity API calls for groups, memberships, devices and SSO profiles based on what you ask for.

What does gws-cloudidentity need to run?

The gws CLI with configured authentication, confirmed with gws auth status, plus the ../gws-shared/SKILL.md file holding auth and global flag rules.

Source text

gws-cloudidentity.md · MIT
---
allowed-tools: Bash, Read, Write, Edit
argument-hint: "[resource] [method] [flags]"
description: "Google Cloud Identity: Manage identity groups and memberships."
---

# Google Workspace Cloudidentity

Execute Google Workspace Cloudidentity operations: $ARGUMENTS

## Prerequisites

- Google Workspace CLI (`gws`) must be installed
- Authentication configured: Run `gws auth status` to verify
- Review `gws cloudidentity --help` for all available commands

## Available Resources and Methods

# cloudidentity (v1)

> **PREREQUISITE:** Read `../gws-shared/SKILL.md` for auth, global flags, and security rules. If missing, run `gws generate-skills` to create it.

```bash
gws cloudidentity <resource> <method> [flags]
```

## API Resources

### customers

  - `userinvitations` — Operations on the 'userinvitations' resource

### devices

  - `cancelWipe` — Cancels an unfinished device wipe. This operation can be used to cancel device wipe in the gap between the wipe operation returning success and the device being wiped. This operation is possible when the device is in a "pending wipe" state. The device enters the "pending wipe" state when a wipe device command is issued, but has not yet been sent to the device. The cancel wipe will fail if the wipe command has already been issued to the device.
  - `create` — Creates a device. Only company-owned device may be created. **Note**: This method is available only to customers who have one of the following SKUs: Enterprise Standard, Enterprise Plus, Enterprise for Education, and Cloud Identity Premium
  - `delete` — Deletes the specified device.
  - `get` — Retrieves the specified device.
  - `list` — Lists/Searches devices.
  - `wipe` — Wipes all data on the specified device.
  - `deviceUsers` — Operations on the 'deviceUsers' resource

### groups

  - `create` — Creates a Group.
  - `delete` — Deletes a `Group`.
  - `get` — Retrieves a `Group`.
  - `getSecuritySettings` — Get Security Settings
  - `list` — Lists the `Group` resources under a customer or namespace.
  - `lookup` — Looks up the [resource name](https://cloud.google.com/apis/design/resource_names) of a `Group` by its `EntityKey`.
  - `patch` — Updates a `Group`.
  - `search` — Searches for `Group` resources matching a specified query.
  - `updateSecuritySettings` — Update Security Settings
  - `memberships` — Operations on the 'memberships' resource

### inboundOidcSsoProfiles

  - `create` — Creates an InboundOidcSsoProfile for a customer. When the target customer has enabled [Multi-party approval for sensitive actions](https://support.google.com/a/answer/13790448), the `Operation` in the response will have `"done": false`, it will not have a response, and the metadata will have `"state": "awaiting-multi-party-approval"`.
  - `delete` — Deletes an InboundOidcSsoProfile.
  - `get` — Gets an InboundOidcSsoProfile.
  - `list` — Lists InboundOidcSsoProfile objects for a Google enterprise customer.
  - `patch` — Updates an InboundOidcSsoProfile. When the target customer has enabled [Multi-party approval for sensitive actions](https://support.google.com/a/answer/13790448), the `Operation` in the response will have `"done": false`, it will not have a response, and the metadata will have `"state": "awaiting-multi-party-approval"`.

### inboundSamlSsoProfiles

  - `create` — Creates an InboundSamlSsoProfile for a customer. When the target customer has enabled [Multi-party approval for sensitive actions](https://support.google.com/a/answer/13790448), the `Operation` in the response will have `"done": false`, it will not have a response, and the metadata will have `"state": "awaiting-multi-party-approval"`.
  - `delete` — Deletes an InboundSamlSsoProfile.
  - `get` — Gets an InboundSamlSsoProfile.
  - `list` — Lists InboundSamlSsoProfiles for a customer.
  - `patch` — Updates an InboundSamlSsoProfile. When the target customer has enabled [Multi-party approval for sensitive actions](https://support.google.com/a/answer/13790448), the `Operation` in the response will have `"done": false`, it will not have a response, and the metadata will have `"state": "awaiting-multi-party-approval"`.
  - `idpCredentials` — Operations on the 'idpCredentials' resource

### inboundSsoAssignments

  - `create` — Creates an InboundSsoAssignment for users and devices in a `Customer` under a given `Group` or `OrgUnit`.
  - `delete` — Deletes an InboundSsoAssignment. To disable SSO, Create (or Update) an assignment that has `sso_mode` == `SSO_OFF`.
  - `get` — Gets an InboundSsoAssignment.
  - `list` — Lists the InboundSsoAssignments for a `Customer`.
  - `patch` — Updates an InboundSsoAssignment. The body of this request is the `inbound_sso_assignment` field and the `update_mask` is relative to that. For example: a PATCH to `/v1/inboundSsoAssignments/0abcdefg1234567&update_mask=rank` with a body of `{ "rank": 1 }` moves that (presumably group-targeted) SSO assignment to the highest priority and shifts any other group-targeted assignments down in priority.

### policies

  - `get` — Get a policy.
  - `list` — List policies.

## Discovering Commands

Before calling any API method, inspect it:

```bash
# Browse resources and methods
gws cloudidentity --help

# Inspect a method's required params, types, and defaults
gws schema cloudidentity.<resource>.<method>
```

Use `gws schema` output to build your `--params` and `--json` flags.

## Usage

```bash
# List available resources and methods
gws cloudidentity --help

# Inspect method schema before calling
gws schema cloudidentity.<resource>.<method>

# Execute command with arguments
gws cloudidentity $ARGUMENTS
```

## Task

Execute the requested Cloudidentity operation: $ARGUMENTS

1. **Verify Prerequisites**
   - Check `gws` is installed: `gws --version`
   - Verify authentication: `gws auth status`
   - Review available commands: `gws cloudidentity --help`

2. **Inspect Method Schema**
   - Before calling any method, inspect its parameters
   - Use `gws schema` to understand required fields
   - Review parameter types and constraints

3. **Execute Operation**
   - Build command with appropriate flags
   - Use `--params` for query/path parameters
   - Use `--json` for request body
   - Handle pagination with `--max-results` or `--page-token`

4. **Error Handling**
   - Check command output for errors
   - Review API quotas and rate limits
   - Handle authentication issues
   - Retry transient failures

---

**License**: Apache License 2.0
**Source**: [Google Workspace CLI](https://github.com/googleworkspace/cli)
**Original Skill**: `gws-cloudidentity`

© davila7 · MIT · davila7/claude-code-templates

Similar slash commands

Everything for Cloud: AWS, Azure, GCP →

From the same set361

The whole set →

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor