From d956264f80b59f54e0609d5a5c1b178d9c52945a Mon Sep 17 00:00:00 2001 From: jesscetera Date: Mon, 12 Oct 2026 19:24:09 +0000 Subject: [PATCH] Document asynchronous enterprise credential deletion (#63782) Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com> --- .../respond-to-incidents/revoke-authorizations-or-tokens.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/content/admin/managing-iam/respond-to-incidents/revoke-authorizations-or-tokens.md b/content/admin/managing-iam/respond-to-incidents/revoke-authorizations-or-tokens.md index ee634ed1b72b..e6dbee7e103a 100644 --- a/content/admin/managing-iam/respond-to-incidents/revoke-authorizations-or-tokens.md +++ b/content/admin/managing-iam/respond-to-incidents/revoke-authorizations-or-tokens.md @@ -102,6 +102,9 @@ Deleting keys and tokens removes credentials that have access to your enterprise {% ifversion single_user_cred_revocation %}For example, you can delete all {% data variables.product.pat_generic_plural %} for an individual member without affecting that member's SSH keys.{% endif %} To restore programmatic access, users must create new credentials, authorize them with organizations if required, and update affected processes to use the new credentials. +> [!WARNING] +> The "Delete keys and tokens" action is not a point-in-time operation. Credential deletion runs asynchronously and processes enterprise members in batches. Credentials created after the action starts may also be deleted if processing is still underway. To avoid deleting replacement credentials, create them only after the operation has finished. + ### Included credentials Both actions include the following credential types: