ThisCalculator

Everyday

How to Revoke an Ai Agents Access to Google Workspace Slack and Github

Updated · Standard formula, shown below

This guide walks you through removing an AI agent’s access to Google Workspace, Slack, and GitHub—a critical step when you decommission a bot, suspect a security issue, or simply want to tighten permissions. You’ll learn the exact steps for each platform, plus how to verify the revocations took effect and what to do if something goes wrong.

What You’ll Need

  • Admin access to each platform: Google Workspace admin console, Slack workspace admin (or owner), and GitHub organization owner or repository admin.
  • The exact name or email/username of the AI agent (e.g., a service account email, a Slack bot token name, or a GitHub app name).
  • If the agent uses OAuth, you’ll need the OAuth client ID or app name. If it uses API keys, you’ll need to identify which key belongs to the agent.

Step-by-Step

Google Workspace

  1. Identify the access type. AI agents typically access Google Workspace via a service account (with domain-wide delegation), an OAuth client, or a third-party app connected by a user. Check the Google Admin console under Security > API controls > Manage Domain Wide Delegation for service accounts. For OAuth apps, go to Security > API controls > Manage Third-Party App Access.
  2. Revoke a service account’s domain-wide delegation. In the Manage Domain Wide Delegation page, find the client ID of the service account, click View Details, then Delete to remove the delegation. This stops the service account from impersonating users.
  3. Revoke an OAuth app’s access. In Manage Third-Party App Access, find the app, click it, and choose Change Access > Block or Restrict. Blocking prevents new uses; to revoke existing tokens, you may need to force a re-auth by changing the app’s trust settings or using the OAuth consent screen.
  4. Delete the service account itself (optional). If the agent is no longer needed, go to Google Cloud Console > IAM & Admin > Service Accounts, select the account, and Delete. This is the most thorough removal.

Slack

  1. Find the agent’s app. Go to Settings & Administration > Manage Apps (or Apps > Manage). Search for the AI agent’s app name.
  2. Revoke the app’s access. Click the app, then select Remove App. This uninstalls the app and revokes all its tokens and permissions. If the app uses a bot token, this also invalidates that token.
  3. If you only want to restrict permissions (not remove entirely), go to the app’s configuration page, click Permissions, and change the OAuth scopes. However, removing the app is the surest way to revoke all access.
  4. Delete the bot user (if separate). In the app configuration, under Bot Users, you can remove the bot, but this is usually done via the app removal.

GitHub

  1. Determine the access type. AI agents often use a GitHub App, an OAuth App, or a Personal Access Token (PAT). Check your organization’s Settings > Applications for installed GitHub Apps and OAuth Apps.
  2. Revoke a GitHub App. In Organization settings > Applications > Installed GitHub Apps, find the agent’s app, click Configure, then scroll to the bottom and click Uninstall. This removes the app’s access to all repositories.
  3. Revoke an OAuth App. In the same Applications page, under OAuth Apps, find the app and click Revoke. This invalidates all user tokens associated with that app.
  4. Delete or revoke a Personal Access Token. If the agent uses a PAT, go to the user account that owns the token (often a service account), navigate to Settings > Developer settings > Personal access tokens, and either delete the token or click Revoke. For fine-grained tokens, you can also edit the token to remove repository access.

Common Mistakes

  • Only removing the app from one workspace/repo but not the others. An AI agent might be installed in multiple Slack workspaces or GitHub organizations. Check all locations.
  • Forgetting about service account keys. In Google Cloud, a service account may have API keys or JSON key files that still work even after removing domain-wide delegation. Delete those keys.
  • Not revoking OAuth tokens after blocking an app. Blocking an app in Google Workspace prevents new authorizations but doesn’t always invalidate existing tokens. You may need to force re-authentication or wait for token expiration.
  • Deleting a Slack app but leaving its bot user active. Removing the app should remove the bot, but double-check under Manage Apps that no residual entries exist.

Tips

  • Audit first. Before revoking, list all access points the agent has. Use admin logs (Google Workspace audit log, Slack audit log, GitHub audit log) to see where the agent has been active.
  • Use a dedicated service account for AI agents. If you’re setting up a new agent, create a separate service account or GitHub app so you can revoke it without affecting other tools.
  • Document the revocation. Note the date and what was revoked, especially if you’re doing this for compliance or security reviews.
  • Test after revocation. Try using the agent’s credentials or making an API call to confirm it fails.

Troubleshooting

  • The agent still appears active. Wait a few minutes for changes to propagate. If it persists, check if there are multiple tokens or app installations. For Google Workspace, ensure you deleted the service account itself, not just the delegation.
  • You can’t find the app in the admin console. The agent might be using a user’s OAuth token rather than an installed app. Check the user’s account under Security > Connected apps (for Google) or Settings > Authorized OAuth Apps (for GitHub).
  • You get an error when trying to uninstall. Make sure you have the necessary admin rights. In Slack, only workspace owners can uninstall apps; in GitHub, only organization owners can uninstall GitHub Apps.
  • After revocation, the agent still has access to a specific file/repo. This could be due to a shared link or a direct permission grant. Check the file/repo’s sharing settings and remove the agent’s email/username explicitly.

Frequently Asked Questions

Will revoking access delete the AI agent’s data or files?

No, revoking access only prevents future access. Files already created or stored by the agent remain in your workspace/repositories. You’ll need to delete them separately if desired.

How long does it take for the revocation to take effect?

Usually immediate, but some systems may take a few minutes to propagate. For Google Workspace, changes to OAuth scopes can take up to 24 hours to fully enforce for existing tokens.

Can I revoke access temporarily and restore it later?

Yes, for most platforms you can re-authorize an app or service account later. However, for GitHub Apps, uninstalling removes all configurations, so you’d need to reconfigure it if you reinstall.

What if the AI agent uses an API key instead of OAuth?

API keys are typically used for Google Cloud APIs. You can delete the API key in the Google Cloud Console under APIs & Services > Credentials. For Slack and GitHub, API keys are less common; they usually use tokens.

Do I need to revoke access in all three platforms at once?

No, you can revoke in any order. However, if the agent is part of an integrated workflow, it’s best to revoke all at once to avoid partial functionality that might cause errors.

What if I don’t have admin rights?

You’ll need to contact the workspace/organization admin. Without admin rights, you cannot revoke app-level access. For personal tokens, you can revoke your own tokens, but not others’.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.