recipe-create-shared-drive

Automating Google Shared Drive creation involves programmatically provisioning the drive and configuring initial members with assigned roles. This recipe validates inputs and executes idempotent commands to ensure consistent access control across multiple projects.

Managing access control for a Shared Drive is best handled by applying initial member roles during drive provisioning. This recipe validates assigned roles and executes commands with basic error handling to prevent permission drift.

Yes, you need the gws-drive skill to provision a Shared Drive. It provides the underlying Google Workspace Drive integration required to execute the automated provisioning and member management commands.

Yes, you can use this recipe to validate and audit drive permissions across projects. It ensures consistent access control by validating inputs and applying idempotent commands for automated drive provisioning.

Manual Shared Drive setup leads to permission drift because configuring access individually introduces delays and inconsistencies. Automating drive provisioning with idempotent commands ensures members receive correct roles consistently.

Idempotent commands for member management handle basic error handling to prevent duplicate entries, but complex permission overrides may require manual intervention. The recipe focuses on initial drive provisioning and role assignment.