Contact Open demo
Solutions / By identity

Every yes to an AI tool leaves a grant behind

Each “Allow” creates an OAuth grant that outlives the click. nerl0 lists every one of them, shows what it opens and who approved it.

Click “Allow”A user says yes GrantA token is issued ScopeWhat it may do DataFiles, mail, code The click The grant is still valid

Every grant, in one list

nerl0 reads grants from your identity and productivity platforms and puts the app, the scope and the approver in a single table.

How connectors work

OAuth grants

6 apps hold access
AppConnected toScopeApproved byLast usedStatus
OpenAIGoogle DriveRead all filesOHOmar HaddadLast monthActive
ClaudeGitHubRead private repositoriesMCMaya ChenThis weekActive
Slack AISlackRead channels and historyJSJonas SchmidtTodayActive
AtlassianJiraCreate and edit issuesLKLena KrausNeverUnused
Salesforce AICRMRead accounts and contactsOHOmar HaddadOver a year agoStale
CopilotGitHubWrite to repositoriesMCMaya ChenTodayActive

See the whole list, not one tenant at a time

Apps, scopes, approvers and last use, across every connected platform. The rows here are demo data.

A grant does not expire when the interest does

The click takes seconds. The access can last for years.

01Created

Someone clicks “Allow” to try an AI tool. It takes four seconds.

02Used

The tool works. It reads files, mail or code in the user’s name.

03Forgotten

The experiment ends, the person changes teams or leaves. Nothing tells the grant.

04Still valid

The token keeps working. Nobody owns it, nobody sees it, it is never reviewed.

The AWS root access key can perform any action on any resource in the account
Recommended action: Delete the root account access key · Remove access
RemediateAssignCreate a ticket⛓⤓⋮

Detected: The AWS account has a root access key. The root user holds an access key; the root user is not bound by IAM policies and holds every action on every resource. Source: scan e07c354c-4aaa-4e30-b18f-8a1468449688 observed 2026-11-09T06:00:00Z, aws coverage complete.

SeverityCritical
Impact4 crown jewels ·not measurable
Authority paths14 authority paths
EvidenceProvenEvery step is an observed relationship: configured authority. Observed use is reported separately. 2 scans · reproduced
Platforms1 platform
Observed useNo use observedin 30 days of CloudTrail · verify before removing

A scope is a promise about reach

The consent screen shows a short phrase. What the grant can really open depends on everything the approving user can reach.

Read all filesEvery document the user can open, not only the one shown in the chat.
Send mailMail in the user’s name, to anyone, with no one reading the draft.
Read repositoriesPrivate code, including secrets that were committed by mistake.
Offline accessA refresh token, so the tool keeps its access long after the session ends.

The person left. The grant stayed.

Switching off an account does not revoke what that account approved. The directory says offboarded, the tool still holds a working token.

Grants need an owner of their own, and a review that does not depend on anyone remembering.

Directory
LKLena KrausAccount disabled
Single sign-on blocked. Mail forwarded. Laptop returned.
OAuth grants approved by Lena
AtlassianActive
Slack AIActive
OpenAIActive

Find it. Compare it. Revoke it.

Three steps for every grant on the list.

01CollectRead every grant from identity and productivity platforms through read-only connectors.
02CompareMatch each scope with the data the approver can reach, and flag what is unused or orphaned.
03RevokeRemove the grants that reach more than they should. The next scan checks that they are gone.

Questions to ask first

These four are in the Question Library. Activate them and every scan answers again.

Browse all questions
From the Incident TrackerStolen OAuth tokens of a sales chat tool were used to read data in customers’ CRM workspaces.Read the incident →

More solutions

Other ways into the same map of authority.

Browse the Academy

See every grant on your own tools.