How to Review and Revoke a Connected PingRoom Agent
Inspect an agent's identity, recent use, permissions, and home Room, then revoke its access when the connection is no longer needed.
To review or remove an agent connection in PingRoom, open Settings → Connected Agents. Check the agent's identity, last-used value, granted permissions, and home Room. If the connection is stale, unexpected, or no longer needs access, choose Revoke, then confirm. The agent loses account access immediately and can reconnect only after you authorize it again.
This is an account-level offboarding control. It does not delete your PingRoom account, remove people from Rooms, or erase Room history.
Audit the connection before you revoke it
Open PingRoom, go to Settings, and choose Connected Agents. Each active connection can show:
- the robot profile name and handle, when the profile has one;
- whether the identity is verified, email verified, or anonymous;
- when it last used the connection;
- the permissions it holds, such as viewing Rooms or sending Pings; and
- its home Room, when one is assigned.
Older connections can have fewer optional identity or Room details. Missing detail is a reason to verify the connection's purpose, not proof that it is harmful.
Use four questions for a quick review:
- Do I recognize this agent? Match the visible name and handle to the client or tool you authorized.
- Does recent use make sense? An unexpected “last used” time deserves investigation.
- Are the permissions still necessary? Access that was reasonable for setup may be broader than the work still being done.
- Is the home Room still appropriate? Check that its default delivery context still belongs to this workflow.
That sequence follows a familiar access-review pattern. GitHub advises users to review authorized applications and revoke unknown or outdated tokens, while Google recommends reviewing the data and services a linked app can access before keeping the connection.
Revoke one connected agent
Once you have identified the connection:
- In Connected Agents, find the agent you want to remove.
- Read its visible permissions and home Room one last time.
- Choose Revoke.
- In Revoke this agent?, confirm Revoke.
- Wait for Agent revoked and confirm that the agent no longer appears in the active list.
The row disappears while PingRoom sends the revocation request. If the request fails, the connection returns to the list and PingRoom shows an error instead of pretending the revocation succeeded. Keep the app online and repeat the action only after checking the current list.
Pingo the Pigeon, PingRoom's fictional Chief Marketing Officer, is watching the empty key hook. He is not the connected agent, the account owner, or proof that access changed. The person holding the account reviews the grant and confirms the revocation.
Verify the result without creating a new risk
Use a controlled check rather than a real urgent workflow:
| Check | Expected result |
|---|---|
| Refresh Connected Agents | The revoked agent stays absent |
| Ask the old client to list or use PingRoom tools | Its old agent credential is refused |
| Review the intended Room | No new Ping should be sent merely to prove revocation |
| Reconnect later | PingRoom asks you to authorize the agent and choose access again |
The second check is useful only when you control the client and can run it safely. Do not ask an untrusted tool to make a live change just to test that it has lost access.
Revocation stops future use of the PingRoom credential. It cannot make an external service forget data it previously received, so use that service's own deletion or retention controls when that matters. Google makes the same distinction for linked apps: removing access blocks future account access but may not delete data already held by the other service.
Reconnect only after a fresh review
A revoked agent does not regain access by itself. If you decide to use it again, start the normal connection flow, review its requested permissions, choose the Rooms it needs, and authorize the new connection deliberately.
For the technical setup path, see Connecting an MCP Client to PingRoom. Terminal users can follow the separate QR pairing guide. The complete current access contract is in Agent Access.
Open Connected Agents now and review one connection you recognize. Keep it only if the identity, recent use, permissions, and Room access still match a task you intend the agent to perform.
Illustrations are AI-generated editorial scenes featuring Pingo, PingRoom's official mascot and fictional Chief Marketing Officer, with fictional approved PingRoom avatars. The access review is an example, not a customer story or evidence of a specific account. The human team is responsible for product claims and decisions.
PingRoom
Short-form communication.
