Update App Builder identity information

config/_default/menus/main.en.yaml

@@ -2698,10 +2698,10 @@ menu:
       parent: workflows
       identifier: workflows_build
       weight: 1
-    - name: Authentication
-      url: actions/workflows/access/
+    - name: Access and Authentication
+      url: actions/workflows/access_and_auth/
       parent: workflows
-      identifier: workflows_access
+      identifier: workflows_access_and_auth
       weight: 2
     - name: Trigger Workflows
       url: actions/workflows/trigger/
@@ -2759,10 +2759,10 @@ menu:
       parent: app_builder
       identifier: app_builder_build
       weight: 1
-    - name: Authentication
-      url: actions/app_builder/auth/
+    - name: Access and Authentication
+      url: actions/app_builder/access_and_auth/
       parent: app_builder
-      identifier: app_builder_access
+      identifier: app_builder_access_and_auth
       weight: 2
     - name: Queries
       url: actions/app_builder/queries/

content/en/account_management/rbac/granular_access.md

@@ -54,11 +54,11 @@ A user with the `user_access_manage` permission can elevate their access to any
 [10]: /service_management/case_management/settings#granular-access-control
 [11]: /getting_started/integrations/#granular-access-control
 [12]: /reference_tables/#permissions
-[13]: /service_management/app_builder/auth/#restrict-access-to-a-specific-app
+[13]: /actions/app_builder/access_and_auth/#restrict-access-to-a-specific-app
 [14]: /actions/connections/?tab=workflowautomation#connection-credentials
 [15]: /actions/connections/?tab=workflowautomation#connection-groups
 [16]: /actions/datastore/
-[17]: /service_management/workflows/access/#restrict-access-on-a-specific-workflow
+[17]: /actions/workflows/access_and_auth/#restrict-access-on-a-specific-workflow
 [18]: /actions/private_actions
 [19]: /real_user_monitoring
 [20]: /account_management/org_settings/cross_org_visibility/#permissions

content/en/actions/action_interface/_index.md

@@ -51,9 +51,9 @@ You can perform an action using the Action Interface. Let's look at an example w
 4. Click the **List ECS cluster** action.
 5. In the action, in **Connection**, select the connection to the AWS account you want to use. Connections are set up in [Action Catalog][1].
   Bits AI will continue to use the same connection for the duration of the chat session.
-1. In **Region**, select the AWS region where the clusters are hosted.
-2. In **Limit**, enter `5`.
-3. Click **Run**.
+6. In **Region**, select the AWS region where the clusters are hosted.
+7. In **Limit**, enter `5`.
+8. Click **Run**.
   Bits AI runs the action. In this example, it responds with a list of the custer names and ARNs.
 
   Bits AI also suggests additional prompts related to the clusters it retrieved.
@@ -66,7 +66,7 @@ You can rely on the Action Interface to inform you if your action is not configu
 [2]: /actions/connections/?tab=workflowautomation
 [3]: /bits_ai/
 [4]: /account_management/audit_trail/
-[5]: /actions/workflows/access/#action-credentials
+[5]: /actions/workflows/access_and_auth/#action-credentials
 [6]: /actions/connections/#connection-credentials
 [7]: /getting_started/integrations/#permissions
 [8]: https://app.datadoghq.com/actions/ai

content/en/actions/app_builder/auth.md → content/en/actions/app_builder/access_and_auth.md

@@ -3,13 +3,16 @@ title: Access and Authentication
 description: Access and authentication for App builder
 aliases:
     - /service_management/app_builder/auth
+    - /actions/app_builder/auth
 ---
 
-A few tools control access and authentication for apps and their components.
+A few tools control access and authentication for apps and their components. 
 
 ## App execution identity
 
-A published app runs using the Datadog user identity of its author. In edit mode, it runs as the current editor.
+A published app runs using the Datadog user identity of its author. The author is listed both in the **All Apps** view and in **App Properties**.
+
+In edit mode, an app runs as the current editor.
 
 ## Action credentials
 

content/en/actions/connections/_index.md

@@ -123,7 +123,7 @@ The example below shows the **New Connection** dialog box for the OpenAI connect
 
 ### Restrict connection use
 
-To learn how to restrict connection use, see Access and Authentication for [Workflow Automation][4] or [App Builder][15].
+To learn how to restrict connection use, see Access and Authentication for [Workflow Automation][12] or [App Builder][15].
 
 ## HTTP connection
 
@@ -153,7 +153,7 @@ Each connection in the group must have a set of unique identifier tags so that a
 
 ### Create a connection group
 
-<div class="alert alert-info"><strong>Note</strong>: You can only add connections to a group if you have <a href="/service_management/workflows/access/#restrict-access-on-a-specific-connection">Resolver permission</a> for them.</div>
+<div class="alert alert-info"><strong>Note</strong>: You can only add connections to a group if you have <a href="/actions/workflows/access_and_auth/#restrict-access-on-a-specific-connection">Resolver permission</a> for them.</div>
 
 To create a connection group:
 
@@ -202,13 +202,12 @@ To delete a connection group:
 
 [2]: https://app.datadoghq.com/workflow
 [3]: https://app.datadoghq.com/workflow/connections
-[4]: /service_management/workflows/access/#restrict-connection-use
 [6]: /integrations/
 [8]: /service_management/workflows/actions/
 [9]: https://app.datadoghq.com/workflow
 [10]: /actions/connections/http/
 [11]: https://datadoghq.slack.com/
-[12]: /service_management/workflows/access/#restrict-access-on-a-specific-connection
+[12]: /actions/workflows/access_and_auth/#restrict-access-on-a-specific-connection
 [13]: /getting_started/tagging/
 [14]: https://app.datadoghq.com/app-builder/
-[15]: /service_management/app_builder/auth/
+[15]: /actions/app_builder/access_and_auth/#restrict-access-to-a-specific-connection

content/en/actions/connections/http.md

@@ -20,14 +20,18 @@ To add an HTTP Request:
 - In a new workflow, click **Add step** and search for `Make request`. Select the **Make request** action to add it to your workflow.
 - In an existing workflow, click **+** and search for `Make request`. Select the **Make request** action to add it to your workflow.
 
-Specify the request method and any necessary [authentication][2]. Read the sections below for further information about the available configuration options. Optionally, the request can wait on conditions that you specify in the **Conditional wait** section, and retry at a given interval if the condition is not satisfied.
+Specify the request method and any necessary [authentication][1]. Read the sections below for further information about the available configuration options. Optionally, the request can wait on conditions that you specify in the **Conditional wait** section, and retry at a given interval if the condition is not satisfied.
+
+[1]: /actions/workflows/access_and_auth/
 {{% /tab %}}
 
 {{% tab "App Builder" %}}
 1. In your app, under **Data**, click **+ New** and select **Query**
 1. Search for `HTTP`, then select the **Make request** action to add it to your app.
 
-Specify the request method and any necessary [authentication][7]. Read the sections below for further information about the available configuration options.
+Specify the request method and any necessary [authentication][1]. Read the sections below for further information about the available configuration options.
+
+[1]: /actions/app_builder/access_and_auth/
 {{% /tab %}}
 {{< /tabs >}}
 
@@ -183,9 +187,7 @@ To configure a private HTTP request:
 <br>Do you have questions or feedback? Join the **#workflows** or **#app-builder** channel on the [Datadog Community Slack][4].
 
 [1]: https://docs.datadoghq.com/api/latest/ip-ranges/#list-ip-ranges
-[2]: /service_management/workflows/access/
 [3]: https://learn.microsoft.com/en-us/azure/active-directory/develop/scopes-oidc#the-default-scope
 [4]: https://datadoghq.slack.com/
 [5]: /actions/private_actions
-[6]: /actions/private_actions/private_action_credentials/?tab=httpsaction#credential-files
-[7]: /service_management/app_builder/auth/
+[6]: /actions/private_actions/private_action_credentials/?tab=httpsaction#credential-files

content/en/actions/workflows/access.md → content/en/actions/workflows/access_and_auth.md

@@ -5,6 +5,7 @@ aliases:
 - /workflows/access
 - /workflows/service_accounts
 - /service_management/workflows/access
+- /actions/workflows/access
 algolia:
   tags: ['workflow', 'workflows', 'workflow automation']
 disable_toc: false

content/en/actions/workflows/trigger.md

@@ -10,7 +10,7 @@ further_reading:
 - link: "/getting_started/workflow_automation/"
   tag: "Documentation"
   text: "Getting Started with Workflow Automation"
-- link: "/service_management/workflows/access/#service-accounts/"
+- link: "/actions/workflows/access_and_auth/#use-a-service-account"
   tag: "Documentation"
   text: "Find out more about Service Accounts for workflows"
 - link: "dashboards"
@@ -273,7 +273,7 @@ After you trigger a workflow, the workflow page switches to the workflow's **Run
 
 <br>Do you have questions or feedback? Join the **#workflows** channel on the [Datadog Community Slack][7].
 
-[1]: /service_management/workflows/access/#use-a-service-account
+[1]: /actions/workflows/access_and_auth/#use-a-service-account
 [2]: https://app.datadoghq.com/monitors/manage
 [3]: https://app.datadoghq.com/security/configuration/notification-rules
 [4]: /security/cloud_security_management/workflows

content/en/getting_started/workflow_automation/_index.md

@@ -4,7 +4,7 @@ further_reading:
     - link: "https://www.datadoghq.com/blog/automate-end-to-end-processes-with-datadog-workflows/"
       tag: "Blog"
       text: "Automate end-to-end processes and quickly respond to events with Datadog Workflows"
-    - link: "/service_management/workflows/access/"
+    - link: "/actions/workflows/access_and_auth/"
       tag: "Documentation"
       text: "Access and authentication"
     - link: "/security/cloud_security_management/workflows/"