[charlotte-hoblik]

Summary

In Stack 9.6 and later, a user-managed service account can call the Agent Builder APIs with a service token, using its own identity and privileges. Serverless can't create these accounts, so every new section is scoped stack: ga 9.6+ and serverless: unavailable.

Closes elastic/docs-content-internal#2137.

What changed

Page	Change
permissions.md	New Service accounts section under Configure access, covering authentication and required privileges. New Service accounts in conversations section under Conversation access control, covering ownership, public conversations, and adding the account as a member. The member role links to it.
kibana-api.md	New Chat as a service account example. The Update conversation access control example now covers service account member IDs.
chat.md	New Messages from a service account subsection, including how a workflow can set author_name. Share a conversation now notes that service accounts don't appear in the user search, are hidden from the member lists, and count toward the sharing button total.
programmatic-access.md	One line pointing service account clients to permissions.md.

Dependency

How to create a user-managed service account and its token is documented in #8921. % comments in permissions.md and kibana-api.md mark where to link authenticate-kibana-api-with-service-account.md after #8921 merges. Until then, the token link points to the existing service accounts page, which covers built-in accounts only.

[github-actions]

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

• Review docs changes (docs-review). Status: not started.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

[github-actions]

🔍 Preview links for changed docs

• explore-analyze/ai-features/agent-builder/chat.md
• explore-analyze/ai-features/agent-builder/kibana-api.md
• explore-analyze/ai-features/agent-builder/permissions.md
• explore-analyze/ai-features/agent-builder/programmatic-access.md

[github-actions]

Elastic Docs Style Checker (Vale)

Summary: 1 suggestion found

💡 Suggestions (1): Optional style improvements. Apply when helpful.

File	Line	Rule	Message
explore-analyze/ai-features/agent-builder/kibana-api.md	1522	Elastic.WordChoice	Consider using 'efficiently' instead of 'simply', unless the term is in the UI.

---

The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.