# Remove user from project IAM bindings in Google Cloud Platform

> A Slack request finds every IAM binding for a departing user across specified GCP projects and removes each one.

Source: https://stepwork.com/marketplace/remove-user-from-project-iam-bindings-in-google-cloud-platform

Automatically remove a user from project IAM bindings in Google Cloud from a Slack request with Stepwork, without a project-by-project hunt.

**Apps:** Google Cloud Platform
**Starts with:** Slack request
**Use case:** Employee offboarding
**Best for:** Cloud Administrator, IT Manager
**Applications used:** Google Cloud Platform, Slack
**Business outcome:** Risk reduction

## One person. IAM bindings scattered across projects.

Cloud access is granted project by project. When someone leaves, an admin has to open each project’s IAM page and remove that principal by hand.

Miss one project and production still trusts a leaver’s account. There is rarely a single record of when GCP access fully ended.

## Complete GCP access removal without a project-by-project hunt

Stepwork finds all IAM bindings for the user in the specified GCP projects and removes each one. The run records who asked and which projects were cleared.

- Every matching binding in the listed projects is removed.
- Projects with no binding for that user are skipped cleanly.
- If a project cannot be opened, the run stops instead of guessing.

## From Slack request to cleared GCP IAM bindings

A teammate posts the user and projects in Slack. Stepwork removes their IAM bindings in Google Cloud Platform.

1. **Request it in Slack** (Slack): A teammate posts the user’s email and the GCP projects to clear in the offboarding channel. That message starts the flow, and Stepwork records who asked and when.
2. **Open each project IAM page** (Google Cloud Platform): Stepwork signs in to Google Cloud Platform and opens IAM for each named project. If a project cannot be found, the run stops.
3. **Remove the bindings** (Google Cloud Platform): Stepwork finds every binding for that user and removes each one, the same edits a cloud admin would make project by project.
4. **Confirm and reply in Slack** (Slack): Stepwork checks that the principal no longer appears on those IAM pages, then posts which projects were cleared.

## Cloud offboarding stays on the path you recorded

A deterministic agent runs the GCP IAM removal path you recorded. Access ends across the listed projects in one run, not across a week of tickets.

## Questions

**Q: How do I remove someone from GCP project IAM bindings automatically?**
Post their email and the projects in Slack. Stepwork removes every matching binding and replies with the projects cleared.

**Q: Does this also grant access for a new hire?**
No. Granting a project IAM role to a user in Google Cloud Platform is a separate access flow.

**Q: What about AWS access for the same departure?**
Cloud offboarding in AWS is covered by separate flows such as deactivating an IAM user in AWS.

---

This is the Markdown version of https://stepwork.com/marketplace/remove-user-from-project-iam-bindings-in-google-cloud-platform, built from the same copy as the page. Everything about Stepwork for AI tools: https://stepwork.com/llms.txt. Book a demo: https://calendly.com/shaun-maclellan/1-1-w-shaun-stepwork
