Disconnecting an integration

Summary#

Every connection you make can be removed, from the same screen you made it on, in one click. Disconnecting takes effect immediately, removes the stored permission, and never touches your saved results, reports or scheduled work. What changes is what happens from that moment on: real Search Console figures go back to estimates, and a removed social channel stops accepting posts.

Purpose#

A connection is a standing permission you granted to another company's account. Being able to withdraw it in one click, from the place you granted it, is the minimum a permission model owes you. Nothing here is a support request or a waiting period.

There are also everyday reasons to disconnect that have nothing to do with security: you connected the wrong Google account, a client changed agencies, or you are handing a workspace over. The steps are the same.

Requirements#

• A signed-in Metric Vault account.
• The connection must belong to your account. You cannot remove one a teammate made.

Permissions#

Any signed-in user can remove their own connections. There is no plan gate and no team role requirement.

Two ownership rules decide what you can remove:

• Social channels belong to the person who connected them. They are stored against your address, not against the workspace, so each teammate manages their own.
• The Google connection belongs to the account that made it, and teammates see it through the shared workspace. If a teammate's screen shows Connected but the disconnect does not appear to work for them, the connection belongs to the workspace owner and must be removed from that account.

An account owner with administrator access can also remove a social channel on a customer's behalf. That is a support action, and only an owner can perform it.

Navigation Path#

Dashboard → Account & Team → Integrations

Social channels are removed from the Connected channels card on the same screen.

Step-by-Step Guide#

Disconnect Google Search Console#

1. Go to Dashboard → Account & Team → Integrations.
2. On the Google Search Console + Analytics card, confirm the badge reads Connected and check the Google address shown underneath is the one you mean to remove.
3. Click Disconnect.
4. Confirm at the prompt Disconnect your Google account? Real-data panels will revert to AI estimates. The confirming button is labelled Disconnect.
5. The badge returns to Not connected and the connect button reappears.

Disconnect a social channel#

1. Go to Dashboard → Promote → Social Dashboard.
2. Find the channel in Connected channels.
3. Click Disconnect. The button changes to Removing… while it works.
4. The row returns to Not connected.

If you connected more than one account to the same platform, this removes all of them for that platform.

Remove the browser extension#

Open chrome://extensions/, find Metric Vault and click Remove. Nothing is stored on the Metric Vault side for the extension, so there is nothing else to clean up. See The Chrome extension.

Revoke an API key#

API keys are managed on the account screen rather than the integrations screen, and revoking one is immediate and permanent. See API keys.

What stops working#

Google#

Nothing already saved is rewritten. A report you exported or shared last week still shows the numbers it showed then.

Deleting the cached data is deliberate and occasionally useful on its own. If a Search Console figure looks wrong and you have already fixed the cause, disconnecting and reconnecting clears the stored copy and forces a fresh fetch.

A social channel#

A scheduled post that includes only the removed channel will run, fail on that one channel, and be marked Failed. Cancel it or reconnect first. See Publishing and scheduling posts.

What is never affected#

• Saved results, reports, exports and share links.
• Your credits, plan and usage.
• Team members, seats and workspaces.
• Monitored competitors, rank alerts and scheduled reports.
• Anything on the provider's side. Your posts, properties and account are untouched.

Disconnecting here versus revoking there#

There are two ends to every connection and they are not the same action.

Revoking at the provider without disconnecting here leaves the card reading Connected until the next attempt to use it fails. That is the most common cause of a connection that looks healthy but is not. If you revoke at the provider, disconnect here as well so the interface tells you the truth.

Google access can be reviewed and withdrawn at <https://myaccount.google.com/permissions>.

Does anyone get notified?#

No. Disconnecting sends no email and alerts no teammate. It is recorded in your own activity history, where the Google entry reads Disconnected Google.

On a shared workspace this matters. Teammates see the same Google connection you do, and the first they will know about its removal is that their real-data panels went back to estimates. Tell them. See What teammates share.

Can I undo it?#

Yes, in every case. Reconnecting takes seconds and restores everything the connection provided.

Reconnecting Google means completing the consent screen again. Do complete it rather than dismissing it, because skipping consent is what produces a connection that cannot renew itself later.

Troubleshooting#

FAQs#

Will disconnecting delete my reports? No. Nothing you have saved, exported or shared is touched.

Does disconnecting refund credits? No. Connections cost nothing, so there is nothing to refund. See How credits work.

If I delete my Metric Vault account, are my connections removed? Account deletion is covered in Deleting your account. Revoking access at the provider as well is the thorough thing to do, and takes a moment.

Can support disconnect something for me? An account owner with administrator access can remove a social channel on your behalf, and the action is recorded in the audit log. Google connections and API keys are yours to remove.

Is disconnecting the right fix for an integration that is misbehaving? Usually, yes. Disconnect and reconnect is the standard repair for an expired or revoked permission. See Integration troubleshooting.