Clarify Bits Code sessions are org-wide

[clreaume]

What does this PR do? What is the motivation?

Motivation (WHY): Users repeatedly assume Bits Code sessions are private to the person who started them. This is recurring implicit feedback (a Datadog team asked how to share sessions across users/within a team for context sharing and picking up a teammate's work when they're out of office—which is already possible, since sessions are org-wide by default). The existing docs never state this; the only hint is the Archive for everyone button label, which is easy to miss.

Changes (WHAT): In content/en/bits_ai/bits_code/_index.md:

• Add a new Session visibility subsection stating that Bits Code sessions are shared across your Datadog organization by default, and that anyone in the org can open a session to review it or continue the work.
• Clarify in View and manage sessions that My Sessions is a personalized view of the sessions you're involved in, not a privacy boundary.
• Split the Unwatch session and Archive for everyone controls into a list so their personal vs. org-wide scope is explicit.

Testing/Validation (HOW verified): Documentation-only change. Verified the edited Markdown/HTML (<i> icon shortcodes, list formatting) renders correctly, confirmed no existing internal links pointed to the changed lines, and reviewed the surrounding section for consistency in tone and terminology.

Merge readiness

• Ready for merge

For Datadog employees:

• ⚠️ Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR.
• 🤖 New: Comment with /review to run an automated check that catches common issues before a Documentation team member reviews your PR.

AI assistance

Drafted with Bits Code (Claude Code): located the relevant docs, proposed the wording, and edited the file. Reviewed by a human before merge.

Additional notes

The org-wide-by-default behavior is consistent with the pre-existing Archive for everyone action. If the product also exposes a distinct "all sessions" / org-wide browsing view in the UI, a reviewer may want to add a pointer to it in the new Session visibility subsection.

---

PR by Bits - View session in Datadog

Comment @DataDog to request changes

[datadog-datadog-prod-us1]

View session in Datadog

Bits Code status: ✅ Done

CI Auto-fix: Disabled | Enable

Comment @DataDog to request changes

[datadog-datadog-prod-us1]

I can only run on private repositories.

[github-actions]

Preview links (active after the build_preview check completes)

Modified Files

• https://docs-staging.datadoghq.com/dd/cara.reaume/bits-code-org-wide-sessions/bits_ai/bits_code/