Merge branch 'main' into docs-issue-6801-change-points-discover

Author: florent-leborgne

_search.md

@@ -0,0 +1,45 @@
+---
+description: Change the Kibana interface language from your user menu or profile.
+applies_to:
+  stack: beta 9.5
+  serverless: beta
+products:
+  - id: kibana
+  - id: cloud-serverless
+type: how-to
+---
+
+
+# Change the interface language in {{kib}}
+
+{{kib}} can display its interface in several languages. From the application header, you can select the language you prefer for your current project or deployment.
+
+:::{tip}
+If you're using {{ecloud}}, this setting only applies to the {{kib}} UI of your serverless projects and hosted deployments.
+:::
+
+## Change your interface language
+
+1. Open the user menu from the header.
+2. Select **Language**.
+
+   :::{note}
+   :applies_to: { self: , ece: , eck: }
+   On self-managed, {{ece}}, and {{eck}} deployments of {{kib}}, this option is located on your profile page. To access it, select **Edit profile** from the header's user menu, then find the **Language** section.
+   :::
+
+3. Select your preferred language from the **Display language** menu.
+4. Select **Save changes**.
+5. Refresh the page to apply the selected language.
+
+## If your language isn't available
+
+By default, {{kib}} offers localized versions for [some languages](kibana://reference/configuration-reference/internationalization-settings.md#built-in-and-custom-locales).
+
+On {{ech}}, {{ece}}, {{eck}}, and self-managed deployments, administrators can enable or disable languages, or turn language selection off, in the [internationalization settings](kibana://reference/configuration-reference/internationalization-settings.md).
+
+## Related pages
+
+- [Internationalization settings in {{kib}}](kibana://reference/configuration-reference/internationalization-settings.md)
+- [Use dark mode in {{kib}}](dark-mode.md)
+- [Use high-contrast mode in {{kib}}](high-contrast.md)

cloud-account/change-interface-language.md

@@ -8,4 +8,5 @@ toc:
   - file: multifactor-authentication.md
   - file: switch-organizations.md
   - file: dark-mode.md
-  - file: high-contrast.md
+  - file: high-contrast.md
+  - file: change-interface-language.md

cloud-account/toc.yml

@@ -56,6 +56,31 @@ You should run `make setup` every time you begin work on a contribution, because
 ::::{step} Make your docs changes
 Edit the relevant TypeScript files in the `specification` directory. Use JSDoc comments to describe your API interfaces, following the [guidelines](./guidelines.md). Add or update summaries, descriptions, tags, metadata, links, and examples as needed.
 ::::
+
+::::{step} Format your changes
+```shell
+make spec-format-fix
+```
+Run this command to format your changes according to the standard used in the specification.
+::::
+
+::::{step} Open a pull request
+
+Once you're satisfied with your docs changes:
+1. Create a pull request from a branch on your local clone
+2. Do not include generated files in the PR, including files under `output/` and `docs/examples/languageExamples.json`. CI regenerates these files, and committing them can cause backport jobs to fail.
+3. The CI will generate the output and validate your additions
+4. Once approved, merge your changes and ensure they are backported to the appropriate branches
+::::
+
+:::::
+
+This is everything that is needed to contribute to the spec, as most validation is performed by CI. 
+If you need to preview the changes locally and check how they'll be displayed in Bump, then a few more steps are needed.
+
+## Generate a Bump preview
+
+:::::{stepper}
 ::::{step} Format, generate and validate your changes
 ```shell
 make contrib
@@ -118,14 +143,7 @@ Run these commands to generate short-lived previews:
 bump preview output/openapi/elasticsearch-openapi-docs-final.json # Preview Elasticsearch API docs
 bump preview output/openapi/elasticsearch-serverless-openapi-docs-final.json # Preview Elasticsearch serverless API docs
 ```
-::::
-
-::::{step} Open a pull request
-
-Once you're satisfied with your docs changes:
-1. Create a pull request from a branch on your local clone
-2. The CI will validate your OpenAPI specs
-3. Once approved, merge your changes and ensure they are backported to the appropriate branches
+After generating the previews, make sure files under `output/` and `docs/examples/languageExamples.json` are not included in your pull request. CI regenerates these files.
 ::::
 
 :::::

contribute-docs/api-docs/elasticsearch-api-docs-quickstart.md

@@ -38,10 +38,10 @@ All Elastic API docs follow this general pattern:
 flowchart TD
     A[Source files] --> B[OpenAPI documents]
     B --> C[Published documentation]
-    
-    style A fill:#fff2cc
-    style B fill:#e1d5e7
-    style C fill:#dae8fc
+
+    class A warning
+    class B important
+    class C note
 ```
 
 1. **Source files** can be:
@@ -71,16 +71,11 @@ flowchart TD
     C1 -->|published| E["HTML published by Bump.sh"]
     B -->|generated| D[Client libraries]
     B -->|generated| F[REST API spec]
-    
-    style A fill:#fff2cc
-    style F fill:#fff2cc
-    style G fill:#fff2cc
-    style B fill:#d5e8d4
-    style C1 fill:#e1d5e7
-    style C2 fill:#e1d5e7
-    style H fill:#fff2cc
-    style D fill:#dae8fc
-    style E fill:#dae8fc
+
+    class A,F,G,H warning
+    class B success
+    class C1,C2 important
+    class D,E note
 ```
 
 ### Input sources

contribute-docs/api-docs/overview.md

@@ -0,0 +1,5 @@
+All application connections mirror the permissions of the user that authorizes the connection. If you authorize the connection and you have read and write permissions, then so will your connected application. 
+
+When a user's permissions change, the change applies on the next token refresh; changes to a custom role apply immediately.
+
+You can use a secondary user with limited permissions to restrict what the connected application can access. Permissions follow the user who authorizes the connection, so ensure that user is signed in before authorizing it. This user does not need to be the same account used to create the OAuth client or manage application connections.

deploy-manage/_snippets/app-connection-permissions.md

@@ -32,4 +32,4 @@ Depending on the APIs you want to use, the API keys to create are different, and
 | [](api-keys/elasticsearch-api-keys.md) | {applies_to}`stack: ga` | • Use [{{es}}]({{es-apis}}) and [{{kib}}]({{kib-apis}}) APIs in stack-versioned deployments, including ECH, ECE, ECK, and self-managed clusters.<br><br>• Manage remote cluster connections. |
 | [](api-keys/serverless-project-api-keys.md) | {applies_to}`serverless: ga`| Use [{{es}} {{serverless-short}}]({{es-serverless-apis}}) and [{{kib}} {{serverless-short}}]({{kib-serverless-apis}}) APIs. |
 | [](api-keys/elastic-cloud-api-keys.md) | {applies_to}`ess: ga` {applies_to}`serverless: ga` | • Manage your {{ecloud}} organization, {{ech}} deployments, and {{serverless-short}} projects using the [{{ecloud}}]({{cloud-apis}}) and [{{ecloud}} {{serverless-short}}]({{cloud-serverless-apis}}) APIs.<br><br>• {applies_to}`serverless: ga` Use [{{es}} {{serverless-short}}]({{es-serverless-apis}}) and [{{kib}} {{serverless-short}}]({{kib-serverless-apis}}) APIs. Using {{ecloud}} keys for project-level API access allows you to create keys that can interact with multiple projects, and manage API access centrally from the {{ecloud}} console. |
-|[](api-keys/elastic-cloud-enterprise-api-keys.md) | {applies_to}`ece: ga` | Manage your {{ece}} platform and deployments using the [{{ece}}]({{ece-apis}}) API. |
+|[](api-keys/elastic-cloud-enterprise-api-keys.md) | {applies_to}`ece: ga` | Manage your {{ece}} platform and deployments using the [{{ece}}]({{ece-apis}}) API. |

deploy-manage/api-keys.md

@@ -0,0 +1,35 @@
+---
+navigation_title: Application connections
+description: Register OAuth clients and manage application connections for authorized access to Elastic Serverless projects.
+type: overview
+applies_to:
+  serverless: preview
+products:
+  - id: cloud-serverless
+  - id: kibana
+---
+
+<!-- this url is referenced in the UI - do not move without a redirect -->
+
+# Application connections [app-connections]
+
+Application connections let users authorize external applications to act on their behalf in {{serverless-short}} projects using OAuth 2.1.
+
+Currently, only MCP clients for the [](/explore-analyze/ai-features/agent-builder/mcp-server.md) are supported. For that use case, OAuth 2.1 replaces static API keys when you need multi-user, delegated access. OAuth tokens are accepted only by the MCP server endpoint.
+
+The sections below describe tasks for registering MCP clients, connecting hosts, revoking access, and managing connections at the project or organization level.
+
+:::{note}
+Application connections are not the same as [{{kib}} connectors](/deploy-manage/manage-connectors.md) or [search connectors](elasticsearch://reference/search-connectors/index.md). {{kib}} connectors store credentials so {{kib}} can send actions to external systems. Search connectors sync data from third-party sources into {{es}}. Application connections allow external systems access to your {{serverless-short}} projects.
+:::
+
+## Before you begin
+
+To choose between an application connection or API keys to authorize external applications for the {{agent-builder}} MCP server, refer to [MCP server authentication](/explore-analyze/ai-features/agent-builder/mcp-server.md#mcp-server-authentication).
+
+## Manage application connections [application-connections-tasks]
+
+Use the following pages to set up and manage application connections for MCP clients:
+
+- [](app-connections/oauth-clients.md): Set up and manage OAuth access for MCP clients, including registering clients, connecting hosts, and revoking access at the project level.
+- [](app-connections/manage-app-connections.md): Audit and revoke authorized connections across your organization's {{serverless-short}} projects in the {{ecloud}} Console.