Keep connected access tidy.

Start in the right workspace

Choose the workspace in PageFluxer before reviewing its settings. Connections belong to that workspace. Owners and admins manage API tokens, browser access and site sessions. Members can review the connections available to them; assistant connections show members only their own authorizations.

• API access: current tokens first, with Revoked tokens below. Only the token prefix and metadata are available after creation.
• Local browsers: current browsers first, with Revoked browsers below.
• Site connections: current sessions first, with Revoked site connections below.
• Assistant connections: active applications first, with Recent connection history for revoked or expired authorizations from the past seven days.

History starts collapsed and shows ten records at a time. Open the section and choose Show more to see additional retained records. Closing it returns the list to its first ten entries. Opening history never restores access or changes a monitor.

Keep problems that need attention visible

An expired API token, a quiet or expired browser, or a site connection with an expired or invalid session stays in the current list until revoked. This helps you find integrations that need a replacement token, a running browser or a fresh sign-in session.

Revoked connections no longer count as active access. Expired or invalid site connections still occupy a site-connection slot until revoked. Your plan limits and the existing history-retention rules continue to apply.

Stop access deliberately

1. Check the connection’s name, workspace and linked monitors or permissions.
2. Use its revoke action and read the confirmation. Integrations relying on that access will stop working.
3. After success, review the record in the history section. Existing monitor history follows the workspace’s normal retention; revoking a credential does not erase it.

API and assistant revocation rejects subsequent authorized requests; work already accepted may finish. Revoking a PageFluxer Local browser blocks uploads immediately, pauses its monitors on the service and stops new checks after the browser observes revocation. Close Chrome or disable the extension to stop local execution immediately.

Revoking a site connection deletes its stored session material and blocks linked signed-in checks. This does not sign the source account out everywhere. Revoke that session on the source website too when needed. Delivered emails, channel messages and third-party copies cannot be recalled.

Reconnect with fresh permission

• API token: create a new token with only the scopes needed, copy it once and update your integration’s secret configuration. A revoked token cannot be recovered.
• PageFluxer Local: connect again from the Chrome extension, then review the monitors assigned to that browser. Reconnecting does not automatically resume previously paused monitors.
• Site connection: use Connect again, supply a new permitted session and confirm a fresh capture before resuming linked monitors. An unused revoked connection can also be removed when it has no linked monitors.
• Assistant: start a new connection from the MCP-compatible application and approve the workspace and scopes again. An owner or admin can revoke any workspace connection; members can revoke only their own.

Understand what history retains

These sections show retained connection metadata, not a permanent security audit log. API-token metadata is bounded and older inactive records may be removed during rotation. Assistant history shows at most 100 recent records; existing cleanup removes authorizations more than seven days after revocation or expiry.

Collapsing history does not delete records, reveal stored credentials or change retention. For capture storage and deletion details, read Security & data handling.