An access review that checks only group membership can approve a connection that no longer exists—and miss one that is still usable.
A ChatGPT Enterprise database connection crosses several control planes:
- enterprise identity
- workspace roles
- connector policy
- MCP tool exposure
- database credentials and grants
- row-level policies
- caches and active sessions
- emergency access
Review the effective path from a real user to a real result.
Then test revocation.
Create a controlled user, establish an active conversation, queue a request, and populate relevant caches. Disable the user and remove the role. Verify:
- new and existing sessions
- queued calls and retries
- refresh tokens
- connector caches
- pooled database connections
- exports and scheduled workflows
A directory change is not complete revocation if an old session can still execute.
Break-glass access deserves the same treatment. Approve one bounded query, let the permission expire, and prove that both the credential and active session are unusable.
The review should change effective access, not just produce a signed spreadsheet.
Full checklist: ChatGPT Enterprise database connection: run an access review that tests reality
Top comments (0)