1단계: 소프트 삭제 상태: 삭제 요청을 시작하면 사용자 및 데이터가 즉시 삭제로 표시되고 30일 소프트 삭제 상태로 전환됩니다. 이 상태에서는 언제든지 데이터를 삭제할 수 있습니다. 삭제 후에는 먼저 복구되지 않는 한 액세스할 수 없습니다. 일반적으로 이 상태의 데이터를 복구할 수 있습니다.
2단계: 영구 삭제 상태: 30일 이상 삭제된 사용자와 데이터는 영구 삭제 상태이며 이는 영구 삭제되어 복구될 수 없음을 의미합니다. 데이터가 삭제된 상태로 전환되면 사용자 식별자를 재사용하고 다른 사용자에게 할당할 수 있습니다. Identity and Access Management(IAM)에서 식별자가 새 항목으로 처리되기 때문입니다.
필수 권한
이 섹션에서는 삭제 및 삭제 취소 작업을 수행하는 데 필요한 IAM 역할 또는 권한에 대해 자세히 설명합니다.
권한은 다음과 같습니다.
iam.googleapis.com/workforcePoolSubjects.delete
iam.googleapis.com/workforcePoolSubjects.undelete
이러한 권한은 직원 풀 관리자 역할(roles/iam.workforcePoolAdmin)에 포함됩니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[[["\u003cp\u003eThis guide explains how to delete workforce users and the data they own on Google Cloud, emphasizing that deleting a user also deletes all their associated data.\u003c/p\u003e\n"],["\u003cp\u003eDeleting users and data involves initiating a delete request using a specific user resource ID format: \u003ccode\u003eprincipal://iam.googleapis.com/locations/<var translate="no">LOCATION</var>/workforcePools/<var translate="no">WORKFORCE_POOL_ID</var>/subject/<var translate="no">SUBJECT_ID</var>\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe data deletion process includes a 30-day soft-deletion state where data can be recovered, followed by a purged state where data is permanently deleted and unrecoverable.\u003c/p\u003e\n"],["\u003cp\u003eYou can recover users and data that are in the soft-deletion state by using the command \u003ccode\u003egcloud iam workforce-pools subjects undelete\u003c/code\u003e, but you need to have the appropriate permissions such as \u003ccode\u003eiam.googleapis.com/workforcePoolSubjects.undelete\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe process to delete workforce users and data is initiated with the command \u003ccode\u003egcloud iam workforce-pools subjects delete\u003c/code\u003e, and it requires you to specify the workforce pool and subject IDs.\u003c/p\u003e\n"]]],[],null,["# Delete Workforce Identity Federation users and their data\n\nThis guide shows you how to delete workforce users (also known as principals)\nand data that they exclusively own, collectively \"users and data\". To learn more\nabout how Google Cloud deletes data, see [Data deletion on Google Cloud](/docs/security/deletion).\n\nDelete Workforce Identity Federation user data\n----------------------------------------------\n\n| **Caution:** Deleting users also deletes all of their data on Google Cloud.\n\nTo delete workforce users and data, you must initiate a delete request with a\nuser resource ID that is formatted as follows: \n\n principal://iam.googleapis.com/locations/\u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e/workforcePools/\u003cvar translate=\"no\"\u003eWORKFORCE_POOL_ID\u003c/var\u003e/subject/\u003cvar translate=\"no\"\u003eSUBJECT_ID\u003c/var\u003e\n\nThe stages in the data-deletion pipeline are as follows:\n\n**Stage-1: Soft-deletion state:** After you initiate a delete request, the\nusers and data are immediately marked for deletion and enter a 30-day soft-\ndeletion state. In that state, the data can be deleted at anytime. After it is\ndeleted, it cannot be accessed unless it is first recovered. You can *usually*\nrecover data that is in this state.\n\n**Stage-2: Purged state:** Users and data that remain deleted longer than 30\ndays are in the purged state, meaning they are permanently deleted and cannot be\nrecovered. After the\ndata enters the purged state, the user identifier can be reused and assigned to\nanother user. This is because the identifier is processed as a new entity in\nIdentity and Access Management (IAM).\n\n### Required permissions\n\nThis section details the IAM roles or permissions required to\nperform delete and undelete operations.\n\nThe permissions are as follows:\n\n- `iam.googleapis.com/workforcePoolSubjects.delete`\n- `iam.googleapis.com/workforcePoolSubjects.undelete`\n\nThese permissions are included in the Workforce Pool Admin role\n(`roles/iam.workforcePoolAdmin`).\n\n### Delete users and data\n\nTo delete users and data, do the following: \n\n### gcloud\n\nExecute the following command: \n\n gcloud iam workforce-pools subjects delete \\\n \u003cvar translate=\"no\"\u003eSUBJECT_ID\u003c/var\u003e \\\n --workforce-pool=\u003cvar translate=\"no\"\u003eWORKFORCE_POOL_ID\u003c/var\u003e \\\n --location=global\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eSUBJECT_ID\u003c/var\u003e: the user resource ID to delete.\n- \u003cvar translate=\"no\"\u003eWORKFORCE_POOL_ID\u003c/var\u003e: the workforce pool ID.\n\n### Undelete users and data\n\nDuring the soft-deletion or pre-purge deletion phase, you can undo a\nuser deletion.\n\nTo undelete a user, do the following: \n\n### gcloud\n\nTo undo a user deletion, execute the following command: \n\n gcloud iam workforce-pools subjects undelete \u003cvar translate=\"no\"\u003eSUBJECT_ID\u003c/var\u003e \\\n --workforce-pool=\u003cvar translate=\"no\"\u003eWORKFORCE_POOL_ID\u003c/var\u003e \\\n --location=global\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eSUBJECT_ID\u003c/var\u003e: the user resource ID for which to undo a previous delete.\n- \u003cvar translate=\"no\"\u003eWORKFORCE_POOL_ID\u003c/var\u003e: the workforce pool ID."]]
