← All guides

Integrations and AI · Taskending editorial team

What happens when you disconnect Gmail?

Disconnecting stops future intake; it does not automatically delete requests already stored as issues.

· 1 min read

How to apply it

An authorized administrator can remove the project Gmail connection. Taskending removes stored Google tokens and stops new intake. Review provider-side application access separately in Google account settings if needed.

A concrete example

When changing a support mailbox, disconnect the old account and connect the new one to the correct project. Existing requests remain as history. Test how the new account handles representative conversations.

What to watch for

Removing the Taskending connection does not delete Gmail messages. Stored Taskending issues and backups follow their own retention rules. Disconnecting an integration is different from deleting an account.

How to check the outcome

Verify the connection is inactive and new messages are no longer imported. Confirm existing request history remains accessible as expected.

Try it in your own workflow.

Create a company workspace and your first issue. Taskending is currently free.

Start for free

Keep reading

01
Integrations and AI

AI task management with Codex and MCP

Connect Codex to issue context through MCP. A human-reviewed workflow for assigned tasks, progress notes, status updates and time tracking.

02
Integrations and AI

How to connect a GitHub repository to Taskending

Signing in with GitHub and connecting a project repository are separate actions. Repository access is authorized separately to associate code events with work.

03
Integrations and AI

Use issue keys in Git branch names

An issue key connects a code change with its reason. Consistent use in branch names makes context easier to find.