Skip to main content

Token Inventory (Asset Management)

Manage the connection between Spikerz and each social account - revoke a token, reconnect a disconnected asset, or remove an asset from the workspace.

Written by Ron Storfer

Introduction

Token Inventory is where you manage the connection between Spikerz and each of your connected social media accounts.

Spikerz protects an account through an API token - the authorization the social platform grants when the account is first connected. While that token is valid, Spikerz can monitor the account around the clock. If the token is revoked or expires, the account becomes disconnected: the account and its history stay in your workspace, but monitoring and automated protection stop until it is reconnected.

The Token Inventory actions live on the All Accounts page. Each account card carries a kebab menu - the three-dot icon in the top-right corner of the card - with the actions needed to keep tokens healthy across an asset's lifetime:

  • Revoke token - disconnect an account and stop monitoring immediately

  • Reconnect - restore a disconnected account's token and resume monitoring

  • Remove asset - permanently delete an account and all its data from the workspace

This guide covers each of those actions, and what to do when an account disconnects on its own.

Before You Start

Make sure that:

  • You are on the All Accounts page (Accounts Summary)

  • The account you want to manage is visible in the account card list

  • You have the role the action requires - some actions are admin-only

Who Can Do What

  • Revoke token - admins only, and only while the account is connected

  • Reconnect - admins and members, and only while the account is disconnected

  • Remove asset - admins only

For more on workspace roles, see How to add admins and members to your workspace.

Revoking a Token

Revoke a token when you want Spikerz to stop monitoring an account without deleting it - for example while an asset is being handed to another team, during an internal review, or before you move the connection to a different platform user.

Revoking is reversible. The account, its alerts, and its history stay in the workspace, and you can reconnect it at any time.

Step 1: Open the kebab menu

On the All Accounts page, locate the account card and select the three-dot menu icon in the top-right corner of the card.

Step 2: Select Revoke token

In the dropdown, select Revoke token. This option appears only for admins, and only while the account is currently connected.

Step 3: Confirm the action

A confirmation dialog appears:

"Revoking this token will disconnect the account and stop all monitoring. You can reconnect it at any time."

Select Revoke token to confirm, or Cancel to go back.

Step 4: Verify the result

The account card updates to a disconnected status with a Reconnect link, and monitoring for that asset stops. A banner also appears at the top of the platform prompting you to reconnect - see the next section.

When an Account Is Disconnected

An account can lose its connection without anyone in Spikerz revoking it. This section explains how you will know, what it means for your protection, and how to get monitoring back.

How You Will Know

A banner at the top of the platform. Whenever one or more of your assets are disconnected, Spikerz shows a red banner across the top of the screen:

"Reconnect X assets to reactivate threats and violations monitoring" - with a Reconnect assets link on the right-hand side.

The number tells you how many assets are currently disconnected. The banner stays visible until every disconnected asset has been reconnected or removed.

Full size preview

The account card. On the All Accounts page, a disconnected account shows a disconnected status in place of its usual health indicators, together with a Reconnect link.

A gap in your alerts. No new alerts are raised for a disconnected asset, so an account that has gone quiet in an otherwise busy feed is worth checking.

Why Accounts Get Disconnected

The most common causes:

  • The token expired. Social platforms issue tokens with a limited lifetime and require periodic re-authorization.

  • The account password was changed on the platform. Many platforms invalidate existing sessions and tokens when credentials change.

  • Security settings changed on the platform - two-factor authentication added or removed, a new device confirmation, or a forced logout of all sessions.

  • Spikerz access was removed on the platform side. If the Spikerz app, or the connecting user's permissions, are removed in the platform's own settings, the token stops working.

  • The connecting user lost access to the asset. A token is tied to a platform user - if that person's role on the page or account is downgraded or removed, the token loses the permissions Spikerz needs.

  • An admin revoked the token in Spikerz, using the action described above.

  • The platform invalidated the token following a policy or API change on their side.

Note: a disconnection is not in itself a sign of compromise - token expiry is routine. But an unexpected disconnection alongside a password, recovery-detail, or 2FA change you do not recognize should be treated as a possible incident. Check the account's feed on the Alerts page before reconnecting.

What Stops While an Account Is Disconnected

Spikerz can only see an account through a valid token. While an asset is disconnected:

  • Threats and violations monitoring pauses - no new detections are made

  • Automated protection and remediation do not run

  • Permissions, roles, and login-activity monitoring stops

  • Comment and DM moderation stops

  • No new alerts are raised for that asset

Your existing data is safe: past alerts, reports, and history remain in the workspace, and monitoring resumes when the asset is reconnected. Depending on the platform, however, activity that took place during the gap may not be recoverable afterwards - which is why reconnecting promptly matters.

Three Ways to Reconnect

Reconnecting works the same way on every platform. There are three routes into it, and all three end at the same place - the platform's own authorization screen, described in How to connect your social account:

  • From the banner - best when several assets are disconnected at once

  • From the account card - best when you are already looking at the asset

  • By adding the account again - works for any asset, on any platform

Pick whichever route you are closest to, then follow Completing the Platform Authorization below.

Route 1: From the Banner

In the red banner at the top of the platform, select Reconnect assets on the right-hand side. Spikerz takes you to the disconnected assets so you can restore them.

Work through them one at a time. Once every disconnected asset is reconnected, the banner disappears. If it is still showing, at least one asset is still disconnected - check the All Accounts page to find which.

Route 2: From the Account Card

Step 1: Open the kebab menu

On the All Accounts page, locate the disconnected account card and select the three-dot menu icon.

Step 2: Select Reconnect

Select Reconnect in the dropdown. This option is available to admins and members, and appears only while the account is disconnected. You can also use the Reconnect link shown directly on the disconnected account card.

Route 3: By Adding the Account Again

Any disconnected asset can also be restored through the standard Add account flow, which takes you back through the platform's authorization. This works for every platform Spikerz supports.

Because the asset already exists in your workspace, adding it again restores the existing asset rather than creating a duplicate - its alerts, reports, history, and settings are preserved.

This route is useful when you are already on the Add account screen, when you need to reconnect several assets across different platforms in one pass, or when the Reconnect action does not complete for some reason.

For the full connect flow, platform by platform, see How to connect your social account. If your workspace connects Meta assets through a system user, see Meta System User Integration.

Completing the Platform Authorization

Whichever route you took, you are redirected to the connect page for that platform. Sign in with the account that holds the required permissions, and approve the Spikerz authorization request. The authorization screens are the same ones covered in How to connect your social account - use that guide if you need the platform-by-platform detail.

Important: reconnect with the same platform user and the same permission scopes that were used originally. Signing in as a different user, or declining any of the requested permissions, can leave the asset only partially connected - some protections will not resume. For what each permission is used for, see the Spikerz Platform Permissions Guide.

Verifying the Reconnection

Back on the All Accounts page, the card should show the account as connected again and the banner should clear. Monitoring resumes automatically - allow a short while for the first scan to complete and for the account's data to repopulate.

If Reconnection Does Not Work

Work through these in order:

  1. Check the permissions on the platform. Open the social platform's own settings and confirm the Spikerz app is still authorized, and that the connecting user still holds an admin-level role on the asset. If your organization manages access through Meta Business Suite, see How to Add Permissions Securely on Meta Business Suite.

  2. Reconnect as the right user. Sign out of the platform in your browser, then start the reconnect flow again and sign in as the user that owns the connection.

  3. Approve every requested permission. Declining even one can block the protections that depend on it.

  4. Try another route. If Reconnect does not complete, add the account again through the Add account flow instead - and vice versa.

  5. Check platform-specific prerequisites. Some platforms need an extra step before Spikerz can connect - for example enabling YouTube permissions. See the Platform Security Features & Availability Guide for what each platform supports.

  6. Retry in a clean browser session. A cached platform session or blocked third-party cookies are a common cause of a flow that ends without an obvious error.

  7. Contact Spikerz support. If the asset still will not reconnect, reach out with the asset name, the platform, and the point in the flow where it fails.

Keeping Tokens Healthy

  • Reconnect promptly. A disconnected asset is an unmonitored asset.

  • Connect through a dedicated user or system user rather than an individual's personal account, so one person leaving does not disconnect your assets.

  • Re-check after platform changes. Password rotations, 2FA changes, and role changes on the platform are the usual triggers - verify your assets are still connected afterwards.

  • Review the All Accounts page regularly, so a disconnection is spotted in the account list rather than in a gap in your alerts.

Removing an Asset

Removing an asset permanently deletes the account and all its associated data from the workspace. Unlike revoking a token, this cannot be undone.

If you only want to stop monitoring for now, revoke the token instead. Remove an asset when the account is being retired, or when it is leaving your workspace for good.

A safety checklist ensures you have updated your login details before removal, so that you are not locked out of an account whose credentials Spikerz manages.

Step 1: Open the kebab menu

On the account card, select the three-dot menu icon.

Step 2: Select Remove asset

Select Remove asset at the bottom of the dropdown - shown in red, as a destructive action. This option is only available to admins.

Step 3: Complete the login details checklist (Step 1 of 2)

If the account has active security features - email, phone, password rotation, or 2FA managed by Spikerz - a checklist dialog appears:

"Before removing this account, make sure you've updated your login details. Skipping these steps may permanently lock you out of your account."

Each applicable item must be checked before you can continue:

If the account has no active security features, this step is skipped automatically.

Step 4: Confirm removal (Step 2 of 2)

A final confirmation dialog appears:

"Are you sure you want to remove {account name} from Spikerz? This will permanently delete all associated data."

Select Remove asset to confirm, or Cancel to go back.

Step 5: Verify the result

The account card disappears from the All Accounts page, and all associated data is deleted from the workspace. To protect the account again later, connect it from scratch through the Add account flow - see How to connect your social account.

Related Articles

Did this answer your question?