1. List connections for each account
  2. Distinguish sign-in from permission
  3. Prepare before revoking
  4. Check what actually stops

List connections for each account

Start from the account’s official settings rather than a link received in a message. Record the app name, developer, current use and visible permissions. Separate tools your team needs from old experiments. An unfamiliar app requires investigation; its name alone does not prove an intrusion. Do not copy tokens, passwords or recovery codes into your inventory.

Distinguish sign-in from permission

Google’s documentation distinguishes using Google to sign in, linking accounts and allowing an app to access Google Account data. These relationships have different effects and directions of access. For another service, read its own labels and explanations. Identify the permitted action: reading, publishing, managing a calendar or accessing files, depending on the options actually shown.

Prepare before revoking

Check how to enter the app if it uses the main account for sign-in. Prepare an alternative offered by the service without weakening account protection. For a team tool, identify dependent tasks and inform their owner. At Google, removing a Sign in with Google connection stops automatic sign-in through that connection but does not delete data held by the app.

Check what actually stops

Google says removing an app’s access to the account may make some features unavailable. Check the outcome in both services and in affected automations. Do not confuse revocation with signing a device out or requesting deletion of data held by the developer. If you want to leave the app, also consult its own procedure and track requests actually completed.

A fictional case to apply the process

Fictional example: a team no longer uses a connected calendar tool. It confirms that no active event depends on it, removes access through the official account and checks scheduled tasks. Closing the developer’s account is a separate process.

Template to adapt

Copy this outline into your working document without passwords or unnecessary personal data.

Affected account, without secret credentials:
App and developer:
Use still needed:
Connection type:
Visible permissions:
Alternative sign-in:
Dependent tasks:
Action completed:
Check in each service:

Your check before use

Checks to complete

0 / 4

Useful questions

Is changing the password enough?

Do not assume this revokes every app. Review connections and sessions in the service’s settings.

Does removing a connection erase app data?

At Google, removing Sign in with Google does not delete data held in the app. Check other services and their procedures separately.

Sources and scope

Sources consulted on 10 October 2026 for the points specified below. The method, template and example are editorial proposals; they are not service tests.