Quick GWS Operator

Multi-service Google Workspace operator for executing cross-platform administrative tasks.

When to Use This Command

Run this command when you need to:

• Perform administrative operations that span multiple Google Workspace services in one command
• Execute common GWS management tasks like user provisioning, group management, or domain settings
• Run diagnostic checks across your Workspace environment to verify service health

Consider alternatives when:

• Your task targets a single GWS service and a dedicated command would be more precise
• You need to perform bulk operations on thousands of users which requires the Admin SDK directly

Quick Start

Configuration

Copy
name: quick-gws-operator
type: command
category: google-workspace

Example Invocation

Copy
claude command:run quick-gws-operator --task "create user [email protected] with Drive and Gmail access"

Example Output

Executing multi-service operation...

Step 1: Create user account
  Service: Admin Directory
  User: [email protected]
  Status: Created successfully

Step 2: Configure Gmail settings
  Service: Gmail
  Delegation: none
  Signature: company template applied
  Status: Configured

Step 3: Set Drive permissions
  Service: Drive
  Shared drives: Engineering, General
  Storage quota: 15 GB
  Status: Configured

Operation complete: 3 steps executed, 0 errors.

Core Concepts

Operator Capabilities Overview

Aspect	Details
User Management	Create, update, suspend, delete users and manage their settings
Group Management	Create groups, manage memberships, set access permissions
Service Config	Configure Gmail, Drive, Calendar settings per user or org unit
Domain Admin	Manage domain verification, security settings, trusted apps
Diagnostics	Check service health, quota usage, license allocation across domain

Operator Workflow

Parse Task Intent
       |
       v
Plan Execution Steps
  (ordered by dependency)
       |
       v
Step 1 --> Service A
       |
       v
Step 2 --> Service B
       |     (uses Step 1 output)
       v
Step 3 --> Service C
       |
       v
Report Results

Configuration

Parameter	Type	Default	Description
task	string	(required)	Natural language description of the administrative task
dry-run	boolean	false	Preview planned steps without executing any changes
org-unit	string	/	Target organizational unit for user or policy operations
confirm	boolean	true	Require confirmation before executing destructive operations
output	string	table	Output format: table, json, or csv

Best Practices

1. Always use dry-run first - Administrative operations often have cascading effects. Preview the planned steps to verify the command interpreted your intent correctly before executing.

2. Scope operations to organizational units - Rather than applying changes domain-wide, target specific org units to limit blast radius and comply with departmental policies.

3. Log all administrative changes - Enable verbose output and save logs for every administrative operation. Audit trails are essential for compliance and troubleshooting.

4. Test with a sandbox user first - Before running user provisioning tasks for real accounts, test with a disposable account to verify all service configurations apply correctly.

5. Chain related operations - Group related tasks like user creation plus group membership plus Drive sharing into a single command to ensure they complete atomically.

Common Issues

1. Insufficient admin privileges - Cross-service operations require super admin or delegated admin roles. Verify your account has the necessary privileges for each target service.

2. Step fails mid-operation - If step 2 of a 3-step operation fails, previous steps have already executed. Use the retry flag to resume from the failed step rather than starting over.

3. Rate limiting across services - Hitting multiple GWS APIs in rapid succession can trigger rate limits. The operator automatically adds delays between steps but long batch operations may still be throttled.