buddyboss/get-account-settings returns a member’s own settings: their notification preferences, profile visibility and messaging rules.
It answers “why is this person not receiving notifications” without guessing.
At a glance
| Ability | buddyboss/get-account-settings |
| Toolset | BuddyBoss — toolset/buddyboss |
| Group | BuddyBoss › Orientation & Reporting |
| Requires | AcrossAI Pro, plus BuddyBoss Platform active on the site |
| Capability | manage_options |
| Safety | Read-only — changes nothing |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Pro 0.9.16 and later |
How it works
These are choices a member made about their own privacy and email. Changing them through an API would override a stated preference silently — the member would start receiving mail they had turned off, or find their profile visible to people they had excluded, with nothing telling them.
So this reads and does not write. If a setting needs changing, the member changes it.
That restraint has a practical payoff too: a support question about missing notifications usually has one of three answers, and two of them are here. Either the member turned that notification off, or their messaging rules exclude the sender, or the site’s mail is broken — and the first two are answerable in one call.
The messaging rules are the ones people forget. A site can restrict messages to connections or to shared-group members, and a member can narrow it further, so “I sent them a message and they never got it” is often a rule rather than a failure.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
user_id | integer | Yes | Whose record this is. Required rather than defaulting, so an administrator’s own account is never acted on by accident. |
What comes back
| Name | Type | What it is |
|---|---|---|
notifications | object | Their notification preferences. |
privacy | object | Profile visibility settings. |
messaging | object | Who may message them. |
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:
Why is this member not getting notifications?
It resolves to one call:
{
"ability": "buddyboss/get-account-settings",
"parameters": {
"user_id": 44
}
}Worth knowing
- Read-only by design — these are the member’s own stated preferences.
- Answers two of the three usual causes of missing notifications.
- Messaging rules explain undelivered messages more often than failures do.
- Changing them is the member’s job.
Related abilities
- BuddyBoss List Notifications — what they were actually sent
- BuddyBoss Search Message Recipients — whether a message can reach them
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category