buddyboss/delete-member deletes a WordPress user account along with everything BuddyBoss holds for them.
Two confirmations, both checked against the live record.
Before you run it
This deletes a person’s whole presence: the account, their profile, their group memberships, their activity, their messages and their uploads. There is no trash and no undo. It requires confirm_user_login — their login, not their display name, because display names are not unique and confirming against one could delete the wrong person — and confirm_content_deletion matching the count of items they produced. Removing them from groups or suspending them is almost always the better answer.
At a glance
| Ability | buddyboss/delete-member |
| Toolset | BuddyBoss — toolset/buddyboss |
| Group | BuddyBoss › Members & Connections |
| Requires | AcrossAI Pro, plus BuddyBoss Platform active on the site |
| Capability | manage_options |
| Safety | Destructive and permanent — deletes the account and everything it produced. Requires two confirmations checked against the live record. |
| Repeatable | Not idempotent — each call changes the row set, so re-running is not a no-op |
| Ships in | AcrossAI Pro 0.9.16 and later |
How it works
The login confirmation is the more interesting one. Display names on BuddyBoss are not unique — two members can legitimately show the same name — so confirming a deletion against a display name could match the wrong account entirely.
The login is unique, which makes it the only safe thing to confirm against.
The content count is the second gate and answers a different question: how much is actually being destroyed. A member who joined last week and a member who has written four thousand posts look identical from an ID, and the count makes the difference visible before rather than after.
Getting it wrong is informative rather than fatal — the refusal reports the real number.
Deleting the account you are signed in as is refused outright.
Suspension and group removal are the alternatives worth considering first. Deletion removes a person’s contributions from every conversation they were part of, which changes threads other people wrote.
Not idempotent.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
user_id | integer | Yes | The member to delete. |
confirm_user_login | string | Yes | Their user_login exactly — not their display name. |
confirm_content_deletion | integer | Yes | The count of items they have produced. The refusal reports the real number. |
confirm | boolean | Yes — must be true | The irreversibility gate. Without it the call is refused before anything is touched. |
What comes back
| Name | Type | What it is |
|---|---|---|
user_id | integer | The account deleted. |
deleted | object | What went with it. |
success | boolean | Whether the call completed. |
message | string | A one-line summary of what happened, suitable for showing a human. |
error_code | string | Present only on failure — a stable machine-readable reason, such as a missing field, a wrong field type or an unmet confirmation. |
Example
Ask your assistant:
Delete this member’s account entirely.
It resolves to one call:
{
"ability": "buddyboss/delete-member",
"parameters": {
"user_id": 44,
"confirm_user_login": "sam.reed",
"confirm_content_deletion": 128
}
}Worth knowing
- Confirm against the login. Display names are not unique.
- The content count makes the scale visible before the deletion, not after.
- Deleting your own account is refused.
- Their contributions vanish from conversations other people wrote.
Related abilities
- BuddyBoss Get Member — confirm who this is
- BuddyBoss Manage Group Membership — remove them from groups instead
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category