BetSlip Doctor

GUIDES · BETSLIP DOCTOR

Why should I confirm my current account before reopening a sensitive conversation?

Confirm which BSD account is currently signed in before reopening a sensitive conversation. The message service uses the authenticated account as its principal, and participant access is checked against that identity. The messaging README also requires client caches to be scoped by actor and cleared on denial or account change. A conversation preview left from another account does not establish that the current account can read the history.

For BSD community members switching accounts before opening private messages · Updated

Check the account that will make the request

Private message access is evaluated for the currently authenticated account. Before opening a sensitive thread, confirm that the account shown by your current product is the one that should participate in that conversation.

A device can be used with different accounts. The device itself does not establish that the current account is an authorized participant.

The current account must pass the conversation checks

The service derives the principal from authenticated request context rather than accepting an account ID supplied in a message request. Conversation history is returned only for an authorized participant under current account and thread checks.

If the request is denied after an account change, rely on that current result. Do not use an older preview or cached history to bypass the check.

Do not reuse a cached thread from another account

The messaging integration guidance says client caches should be scoped to the authenticated actor and cleared on denial or account change, then revalidated against current access.

If you cannot confirm which account is active, pause before reopening sensitive content and use the account controls available in your current BSD client. The source does not establish a universal account-switch screen.

Hypothetical: switching from one account to another

Imagine a person viewed a private conversation under one BSD account, then switches to a different account on the same device. Before reopening the thread, the person verifies the current account. If the new account is not an authorized participant, the person relies on the current denial and does not use the old cached preview.

Related questions

Does using the same device mean I can reopen the same conversation?

No. Access is evaluated for the authenticated account and current participant authority, not just for the device that previously displayed a thread.

Should a previous account's conversation preview remain visible after I switch?

The messaging integration guidance requires actor-scoped caches to clear on account change or denial and to revalidate current access.

Sources and further reading

Explore BSD research.

Review supported ways to use BSD.