Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 8 additions & 4 deletions openbot/docs/plugins/google-drive.md
Original file line number Diff line number Diff line change
Expand Up @@ -92,10 +92,14 @@ expires.

### Disconnecting

**Not built yet.** Until it is, revoke it in Google's own third-party access settings
([myaccount.google.com/connections](https://myaccount.google.com/connections)), which stops this
deployment reading anything immediately. The page says the same thing rather than offering a control
that would report access withdrawn when it had not been.
On the connector's page under **Connections**, open **Connected** and choose **Disconnect**. It
disconnects only the signed-in person's own account, the same way Gmail and Google Calendar do (see
[Disconnecting](google-workspace.md#disconnecting)). It asks Google to revoke the refresh token, then
revokes the stored credential and removes the connection.

- If Google cannot be reached, nothing changes and the page asks you to try again.
- If Google refuses, access still ends in this deployment, and the page tells you to finish at
[myaccount.google.com/connections](https://myaccount.google.com/connections).

## Troubleshooting

Expand Down
12 changes: 9 additions & 3 deletions openbot/docs/plugins/google-workspace.md
Original file line number Diff line number Diff line change
Expand Up @@ -140,9 +140,15 @@ so revoking access at Google takes effect on the next call.

### Disconnecting

**Not built yet.** Until it is, revoke access in Google's own third-party access settings
([myaccount.google.com/connections](https://myaccount.google.com/connections)), which stops this
deployment reading mail or the calendar immediately.
On `/connections/google-workspace`, open **Connected** and choose **Disconnect**. It disconnects only the
signed-in person's own account. It asks Google to revoke the refresh token, then revokes the stored
credential and removes the connection in one transaction, and writes an audit event.

- If Google cannot be reached, nothing changes and the page asks you to try again, so access is never
reported withdrawn when it was not.
- If Google refuses the revocation, access still ends in this deployment, and the page tells you to
finish at Google's own third-party access settings
([myaccount.google.com/connections](https://myaccount.google.com/connections)).

## Trying it without a Google account

Expand Down
Loading