Fix inconsistent reference to the app config file (#1006)

jmagak · web-flow · commit a71e6bcff301 · 2025-03-24T12:05:27.000+05:30
diff --git a/modules/authentication/proc-enabling-authentication-with-github.adoc b/modules/authentication/proc-enabling-authentication-with-github.adoc
@@ -63,8 +63,9 @@ TIP: If you plan to make changes using the GitHub API, ensure that `Read and wri
 `GITHUB_WEBHOOK_URL`:: Enter your {product-short} URL: `pass:c,a,q[{my-product-url}]`.
 `GITHUB_WEBHOOK_SECRET`:: Enter the saved *Webhook secret*.
 
-. To set up the GitHub authentication provider and enable integration with the GitHub API in your {product-short} custom configuration, edit your custom {product-short} ConfigMap such as `app-config-rhdh`, and add the following lines to the `app-config-rhdh.yaml` content:
+. To set up the GitHub authentication provider and enable integration with the GitHub API in your {product-short} custom configuration, edit your custom {product-short} config map such as `{my-app-config-config-map}`, and add the following lines to the `{my-app-config-file}` file content:
 +
+.`{my-app-config-file}` file fragment with mandatory fields to enable authentication with GitHub
 --
 .`app-config-rhdh.yaml` fragment with mandatory fields to enable authentication with GitHub
 [source,yaml]
@@ -135,7 +136,7 @@ dangerouslyAllowSignInWithoutUserInCatalog: true
 The callback URL that GitHub uses when initiating an OAuth flow, such as: __<your_intermediate_service_url/handler>__.
 Define it when {product-short} is not the immediate receiver, such as in cases when you use one OAuth app for many {product-short} instances.
 +
-.`app-config-rhdh.yaml` fragment with optional `enterpriseInstanceUrl` field
+.`{my-app-config-file}` file fragment with optional `enterpriseInstanceUrl` field
 [source,yaml,subs="+quotes"]
 ----
 auth:
@@ -150,7 +151,7 @@ auth:
 Your GitHub Enterprise URL.
 Requires you defined the `GITHUB_HOST_DOMAIN` secret in the previous step.
 +
-.`app-config-rhdh.yaml` fragment with optional `enterpriseInstanceUrl` field
+.`{my-app-config-file}` file fragment with optional `enterpriseInstanceUrl` field
 [source,yaml,subs="+quotes"]
 ----
 auth:
@@ -168,7 +169,7 @@ To enable GitHub integration with a different authentication provider, complete
 * Add the GitHub provider to the existing `auth` section.
 * Keep the `signInPage` section from your authentication provider configuration.
 
-.`app-config-rhdh.yaml` fragment with mandatory fields to enable GitHub integration and use a different authentication provider
+.`{my-app-config-file}` file fragment with mandatory fields to enable GitHub integration and use a different authentication provider
 [source,yaml,subs="+quotes"]
 ----
 auth:
diff --git a/modules/authentication/proc-enabling-authentication-with-microsoft-azure.adoc b/modules/authentication/proc-enabling-authentication-with-microsoft-azure.adoc
@@ -27,8 +27,7 @@
 * `openid`
 * `profile`
 * `User.Read`
-* Optional custom scopes for the Microsoft Graph API that you define both in this section and in the {product-short} configuration (`app-config-rhdh.yaml`).
-+
+* Optional custom scopes for the Microsoft Graph API that you define both in this section and in the `{my-app-config-file}` {product-short} configuration file.
 [NOTE]
 ====
 Your company might require you to grant admin consent for these permissions.
@@ -50,10 +49,10 @@ To grant administrator consent, a directory administrator must go to the link:ht
 `AUTH_AZURE_CLIENT_ID`:: Enter your saved *Application (client) ID*.
 `AUTH_AZURE_CLIENT_SECRET`:: Enter your saved *Application (client) secret*.
 
-. Set up the Microsoft Azure authentication provider in your {product-short} custom configuration, such as `app-config-rhdh`:
+. Set up the Microsoft Azure authentication provider in your `{my-app-config-file}` file:
 +
 --
-.`app-config-rhdh.yaml` fragment
+.`{my-app-config-file}` file fragment
 [source,yaml,subs="+quotes,+attributes"]
 ----
 auth:
@@ -106,7 +105,7 @@ If you want to use this parameter for a single-tenant application, uncomment and
 If your application registration is multi-tenant, leave this parameter blank.
 For more information, see link:https://learn.microsoft.com/en-us/azure/active-directory/manage-apps/home-realm-discovery-policy[Home Realm Discovery].
 +
-.`app-config-rhdh.yaml` fragment with optional `domainHint` field
+.`{my-app-config-file}` file fragment with optional `domainHint` field
 [source,yaml,subs="+quotes,+attributes"]
 ----
 auth:
@@ -122,7 +121,7 @@ Optional for additional scopes.
 To add scopes for the application registration, uncomment and enter the list of scopes that you want to add.
 The default and mandatory value lists: `'openid', 'offline_access', 'profile', 'email', 'User.Read'`.
 +
-.`app-config-rhdh.yaml` fragment with optional `additionalScopes` field
+.`{my-app-config-file}` file fragment with optional `additionalScopes` field
 [source,yaml,subs="+quotes,+attributes"]
 ----
 auth:
diff --git a/modules/authorization/proc-configuring-the-RBAC-backend-plugin.adoc b/modules/authorization/proc-configuring-the-RBAC-backend-plugin.adoc
@@ -1,13 +1,13 @@
 [id="configuring-the-rbac-backend-plugin_{context}"]
 = Configuring the RBAC backend plugin
 
-You can configure the RBAC backend plugin by updating the `app-config.yaml` file to enable the permission framework.
+You can configure the RBAC backend plugin by updating the `{my-app-config-file}` file to enable the permission framework.
 
 .Prerequisites
 * You have installed the `@janus-idp/backstage-plugin-rbac` plugin in {product-short}. For more information, see link:{plugins-configure-book-url}[{plugins-configure-book-title}].
 
 .Procedure
-* Update the `app-config.yaml` file to enable the permission framework as shown:
+* Update the `{my-app-config-file}` file to enable the permission framework as shown:
 
 [source,yaml,subs=+quotes]
 ----
@@ -25,5 +25,5 @@ permission
 
 [NOTE]
 ====
-The `pluginsWithPermission` section of the `app-config.yaml` section includes only three plugins by default. Update the section as needed to include any additional plugins that also incorporate permissions.
+The `pluginsWithPermission` section of the `{my-app-config-file}` file includes only three plugins by default. Update the section as needed to include any additional plugins that also incorporate permissions.
 ====
diff --git a/modules/authorization/proc-defining-authorizations-in-external-files-by-using-helm.adoc b/modules/authorization/proc-defining-authorizations-in-external-files-by-using-helm.adoc
@@ -93,7 +93,7 @@ name::: `rbac-policies`
 
 . Update your {product-short} `{my-app-config-file}` configuration file to use the `rbac-policies.csv` and `rbac-conditional-policies.yaml` external files:
 +
-.`app-config.yml` fragment
+.`{my-app-config-file}` file fragment
 [source,yaml]
 ----
 permission:
diff --git a/modules/authorization/proc-defining-authorizations-in-external-files-by-using-the-operator.adoc b/modules/authorization/proc-defining-authorizations-in-external-files-by-using-the-operator.adoc
@@ -90,9 +90,9 @@ spec:
         - name: rbac-policies
 ----
 
-. Update your {product-short} `app-config.yaml` configuration file to use the `rbac-policies.csv` and `rbac-conditional-policies.yaml` external files:
+. Update your {product-short} `{my-app-config-file}` configuration file to use the `rbac-policies.csv` and `rbac-conditional-policies.yaml` external files:
 +
-.`app-config.yml` fragment
+.`{my-app-config-file}` file fragment
 [source,yaml]
 ----
 permission:
diff --git a/modules/authorization/proc-enabling-the-rbac-plugin.adoc b/modules/authorization/proc-enabling-the-rbac-plugin.adoc
@@ -25,7 +25,7 @@ plugins:
 See link:{installing-and-viewing-dynamic-plugins-url}[{installing-and-viewing-dynamic-plugins-title}].
 
 . Declare policy administrators to enable a select number of authenticated users to configure RBAC policies through the REST API or Web UI, instead of modifying the CSV file directly.
-The permissions can be specified in a separate CSV file referenced in the `app-config-rhdh` ConfigMap, or permissions can be created using the REST API or Web UI.
+The permissions can be specified in a separate CSV file referenced in your `{my-app-config-config-map}` config map, or permissions can be created using the REST API or Web UI.
 +
 To declare users such as _<your_policy_administrator_name>_ as policy administrators, edit your custom {product-short} ConfigMap, such as `app-config-rhdh`, and add following code to the `{my-app-config-file}` content:
 +
diff --git a/modules/authorization/proc-setting-up-the-guest-authentication-provider.adoc b/modules/authorization/proc-setting-up-the-guest-authentication-provider.adoc
@@ -8,7 +8,7 @@ You can enable guest authentication and use it alongside the RBAC frontend plugi
 
 .Procedure
 
-* In the `app-config.yaml` file, add the user entity reference to resolve and enable the `dangerouslyAllowOutsideDevelopment` option, as shown in the following example:
+* In the `{my-app-config-file}` file, add the user entity reference to resolve and enable the `dangerouslyAllowOutsideDevelopment` option, as shown in the following example:
 
 [source,yaml,subs="+attributes,+quotes"]
 ----
@@ -22,5 +22,5 @@ auth:
 
 [NOTE]
 ====
-You can use `user:default/guest` as the user entity reference to match the added user under the `permission.rbac.admin.users` section of the `app-config.yaml` file.
+You can use `user:default/guest` as the user entity reference to match the added user under the `permission.rbac.admin.users` section of the `{my-app-config-file}` file.
 ====
diff --git a/modules/customizing-templates/proc-adding-templates.adoc b/modules/customizing-templates/proc-adding-templates.adoc
@@ -15,7 +15,7 @@ You can add an existing template to your {product} instance by using the Catalog
 
 .Procedure
 
-* In the `app-config.yaml` configuration file, modify the `catalog.rules` section to include a rule for templates, and configure the `catalog.locations` section to point to the template that you want to add, as shown in the following example:
+* In the `{my-app-config-file}` configuration file, modify the `catalog.rules` section to include a rule for templates, and configure the `catalog.locations` section to point to the template that you want to add, as shown in the following example:
 +
 [source,yaml]
 ----
diff --git a/modules/customizing-the-appearance/proc-customize-rhdh-branding-logo.adoc b/modules/customizing-the-appearance/proc-customize-rhdh-branding-logo.adoc
@@ -5,7 +5,7 @@
 [id="proc-customize-rhdh-branding-logo_{context}"]
 = Customizing the branding logo of your {product-short} instance
 
-You can customize the branding logo of your {product-short} instance by configuring the `branding` section the `app-config-rhdh.yaml` file, as shown in the following example:
+You can customize the branding logo of your {product-short} instance by configuring the `branding` section the `{my-app-config-file}` file, as shown in the following example:
 
 [source,yaml]
 ----
diff --git a/modules/customizing-the-appearance/proc-customize-rhdh-font.adoc b/modules/customizing-the-appearance/proc-customize-rhdh-font.adoc
@@ -4,7 +4,7 @@
 [id="proc-customize-rhdh-font_{context}"]
 = Customizing the font for your {product-short} instance
 
-You can configure the `typography` section of the `app-config-rhdh.yaml` file to change the default font family and size of the page text, as well as the font family and size of each heading level, as shown in the following example:
+You can configure the `typography` section of the `{my-app-config-file}` file to change the default font family and size of the page text, as well as the font family and size of each heading level, as shown in the following example:
 
 [source,yaml]
 ----
diff --git a/modules/customizing-the-appearance/proc-customize-rhdh-page-theme.adoc b/modules/customizing-the-appearance/proc-customize-rhdh-page-theme.adoc
@@ -4,7 +4,7 @@
 [id="proc-customize-rhdh-page-theme_{context}"]
 = Customizing the page theme header for your {product-short} instance
 
-You can customize the header color for the light and dark theme modes in your {product-short} instance by modifying the `branding.theme` section of the `app-config-rhdh.yaml` file. You can also customize the page headers for additional {product-short} pages, such as the *Home*, *Catalog*, and *APIs* pages.
+You can customize the header color for the light and dark theme modes in your {product-short} instance by modifying the `branding.theme` section of the `{my-app-config-file}` file. You can also customize the page headers for additional {product-short} pages, such as the *Home*, *Catalog*, and *APIs* pages.
 
 [source,yaml]
 ----
diff --git a/modules/customizing-the-appearance/proc-customize-rhdh-palette.adoc b/modules/customizing-the-appearance/proc-customize-rhdh-palette.adoc
@@ -4,7 +4,7 @@
 [id="proc-customize-rhdh-branding_{context}"]
 = Customizing the theme mode color palettes for your {product-short} instance
 
-You can customize the color palettes of the light and dark theme modes in your {product-short} instance by configuring the `light.palette` and `dark.palette` parameters in the `branding.theme` section of the `app-config-rhdh.yaml` file, as shown in the following example:
+You can customize the color palettes of the light and dark theme modes in your {product-short} instance by configuring the `light.palette` and `dark.palette` parameters in the `branding.theme` section of the `{my-app-config-file}` file, as shown in the following example:
 
 [source,yaml]
 ----
diff --git a/modules/customizing-the-appearance/proc-customize-rhdh-sidebar-menuitems.adoc b/modules/customizing-the-appearance/proc-customize-rhdh-sidebar-menuitems.adoc
@@ -6,7 +6,18 @@ The sidebar menu in {product} consists of two main parts that you can configure:
 Dynamic plugin menu items:: Your preferences and your active plugins define dynamically one part of the sidebar menu.
 Main menu items:: The core navigation structure of sidebar is static.
 
-.Default static menu item configuration
+* *Dynamic plugin menu items*: These items are displayed beneath the main menu and can be customized based on the plugins installed. The main menu items section is dynamic and can change based on your preferences and installed plugins.
+
+.Procedure
+
+. Customize the main menu items using the following steps:
++
+--
+.. Open the `{my-app-config-file}` file.
+.. To customize the order and parent-child relationships for the main menu items, use the `dynamicPlugins.frontend.default.main-menu-items.menuItems` field.
+.. For dynamic plugin menu items, use the `dynamicPlugins.frontend.<package_name>.menuItems` field.
+
+.Example `{my-app-config-file}` file
 [source,yaml]
 ----
 dynamicPlugins:
diff --git a/modules/customizing-the-appearance/proc-loading-custom-theme-using-dynamic-plugin.adoc b/modules/customizing-the-appearance/proc-loading-custom-theme-using-dynamic-plugin.adoc
@@ -24,7 +24,7 @@ For more information about creating a custom theme, see link:https://backstage.i
 
 . Configure {product-short} to load the theme in the UI by using the `themes` configuration field:
 +
-.`app-config-rhdh.yaml` fragment
+.`{my-app-config-file}` fragment
 [source,yaml]
 ----
 dynamicPlugins:
diff --git a/modules/customizing-the-appearance/ref-customize-rhdh-custom-components.adoc b/modules/customizing-the-appearance/ref-customize-rhdh-custom-components.adoc
@@ -11,7 +11,7 @@ There are two component variants that you can use to customize various component
 
 In addition to assigning a component variant to each parameter in the light or dark theme mode configurations, you can toggle the `rippleEffect` `on` or `off`.
 
-The following code shows the options that you can use in the `app-config-rhdh.yaml` file to configure the theme components for your {product-short} instance:
+The following code shows the options that you can use in the link:{configuring-book-url}[`{my-app-config-file}` file] to configure the theme components for your {product-short} instance:
 
 [source,yaml]
 ----
diff --git a/modules/customizing-the-appearance/ref-customize-rhdh-default-backstage.adoc b/modules/customizing-the-appearance/ref-customize-rhdh-default-backstage.adoc
@@ -4,11 +4,11 @@
 [id="ref-customize-rhdh-default-backstage_{context}"]
 = Default Backstage theme
 
-You can use the default Backstage theme configurations to make your {product-short} instance look like a standard Backstage instance. You can also modify the `app-config-rhdh.yaml` file to customize or disable particular parameters.
+You can use the default Backstage theme configurations to make your {product-short} instance look like a standard Backstage instance. You can also modify the `{my-app-config-file}` file to customize or disable particular parameters.
 
 == Default Backstage theme color palette
 
-The `app-config-rhdh.yaml` file uses the following configurations for the default Backstage color palette:
+The `{my-app-config-file}` file uses the following configurations for the default Backstage color palette:
 
 [source,yaml]
 ----
@@ -138,7 +138,7 @@ app:
           warningText: "#000000"
 ----
 
-Alternatively, you can use the following `variant` and `mode` values in the `app-config-rhdh.yaml` file to apply the previous default configuration:
+Alternatively, you can use the following `variant` and `mode` values in the `{my-app-config-file}` file to apply the previous default configuration:
 
 [source,yaml]
 ----
@@ -155,7 +155,7 @@ app:
 
 == Default Backstage page themes
 
-The default Backstage header color is white in light mode and black in dark mode, as shown in the following `app-config-rhdh.yaml` file configuration:
+The default Backstage header color is white in light mode and black in dark mode, as shown in the following `{my-app-config-file}` file configuration:
 
 [source,yaml]
 ----
diff --git a/modules/customizing-the-appearance/ref-customize-rhdh-default-rhdh.adoc b/modules/customizing-the-appearance/ref-customize-rhdh-default-rhdh.adoc
@@ -4,11 +4,11 @@
 [id="ref-customize-rhdh-default-rhdh_{context}"]
 = Default {product} theme
 
-You can use the default {product} theme configurations to make your {product-short} instance look like a standard {product} instance. You can also modify the `app-config-rhdh.yaml` file to customize or disable particular parameters.
+You can use the default {product} theme configurations to make your {product-short} instance look like a standard {product} instance. You can also modify the `{my-app-config-file}` file to customize or disable particular parameters.
 
 == Default {product} theme color palette
 
-The `app-config-rhdh.yaml` file uses the following configurations for the default {product} color palette:
+The `{my-app-config-file}` file uses the following configurations for the default {product} color palette:
 
 [source,yaml]
 ----
@@ -202,7 +202,7 @@ app:
               headerBackgroundImage: "none"
 ----
 
-Alternatively, you can use the following `variant` and `mode` values in the `app-config-rhdh.yaml` file to apply the previous default configuration:
+Alternatively, you can use the following `variant` and `mode` values in the `{my-app-config-file}` file to apply the previous default configuration:
 
 [source,yaml]
 ----
@@ -219,7 +219,7 @@ app:
 
 == Default {product} page themes
 
-The default {product-short} header color is white in light mode and black in dark mode, as shown in the following `app-config-rhdh.yaml` file configuration:
+The default {product-short} header color is white in light mode and black in dark mode, as shown in the following `{my-app-config-file}` file configuration:
 
 [source,yaml]
 ----
diff --git a/modules/customizing-the-home-page/proc-customizing-the-home-page-cards.adoc b/modules/customizing-the-home-page/proc-customizing-the-home-page-cards.adoc
@@ -7,7 +7,7 @@
 
 Administrators can change the fixed height of cards that are in a 12-column grid.
 
-The default Home page is as shown in the following `app-config` file configuration:
+The default Home page is as shown in the following `{my-app-config-file}` file configuration:
 
 [source,yaml]
 ----
diff --git a/modules/customizing-the-home-page/proc-defining-the-layout-of-the-product-home-page.adoc b/modules/customizing-the-home-page/proc-defining-the-layout-of-the-product-home-page.adoc
@@ -14,8 +14,8 @@ The Home page uses a 12-column grid to position your cards. You can use the opti
 ** position (x and y)
 
 .Procedure
-. Configure the layout of the cards on the home page by entering one of the following configurations in your {product-short} `{my-app-config-file}` file.
-* Use the full space on smaller windows and half of the space on larger windows as shown in the following example:
+* Configure your {product-short} `{my-app-config-file}` configuration file by choosing one of the following options:
+** Use the full space on smaller windows and half of the space on larger windows as follows:
 
 [source,yaml]
 ----
diff --git a/modules/customizing-the-learning-paths/proc-customize-rhdh-learning-paths.adoc b/modules/customizing-the-learning-paths/proc-customize-rhdh-learning-paths.adoc
@@ -59,7 +59,7 @@ For more information, see xref:{installing-on-ocp-book-url}#assembly-install-rhd
 
 To use a dedicated service to provide the Learning Path data, complete the following steps:
 
-. Add the following code to the `app-config-rhdh.yaml` file:
+. Add the following code to the link:{configuring-book-url}[`{my-app-config-file}` file]:
 +
 [source,yaml]
 ----
diff --git a/modules/customizing-the-quick-access-card/proc-using-a-dedicated-service-to-provide-data-to-the-quick-access-card.adoc b/modules/customizing-the-quick-access-card/proc-using-a-dedicated-service-to-provide-data-to-the-quick-access-card.adoc
@@ -36,7 +36,7 @@ To use the `red-hat-developer-hub-customization-provider` service, add the URL f
 *Target Port* automatically generates a Kubernetes or {ocp-short} service to communicate with.
 ====
 +
-. Add the following code to the `app-config-rhdh.yaml` file:
+. Add the following code to the link:{configuring-book-url}[`{my-app-config-file}` file]:
 +
 [source,yaml]
 ----
@@ -54,7 +54,7 @@ proxy:
 +
 [NOTE]
 ====
-The `red-hat-developer-hub-customization-provider` service contains the 8080 port by default. If you are using a custom port, you can specify it with the 'PORT' environmental variable in the `app-config-rhdh.yaml` file.
+The `red-hat-developer-hub-customization-provider` service contains the 8080 port by default. If you are using a custom port, you can specify it with the 'PORT' environmental variable in the `{my-app-config-file}` file.
 ====
 +
 . Replace the `HOMEPAGE_DATA_URL` by adding the URL to `rhdh-secrets` or by directly replacing it in your custom ConfigMap.
@@ -111,14 +111,14 @@ If the request call fails or is not configured, the {product-short} instance fal
 
 * If the images or icons do not load, then allowlist them by adding your image or icon host URLs to the content security policy (csp) `img-src` in your custom ConfigMap as shown in the following example:
 
-[source,yaml]
+[source,yaml,subs="attributes+"]
 ----
 kind: ConfigMap
 apiVersion: v1
 metadata:
-  name: app-config-rhdh
+  name: {my-app-config-file}
 data:
-  app-config-rhdh.yaml: |
+  {my-app-config-file}: |
     app:
       title: Red Hat Developer Hub
     backend:
diff --git a/modules/customizing-the-quick-access-card/proc-using-hosted-json-files-to-provide-data-to-the-quick-access-card.adoc b/modules/customizing-the-quick-access-card/proc-using-hosted-json-files-to-provide-data-to-the-quick-access-card.adoc
@@ -13,7 +13,9 @@ See xref:{installing-on-ocp-book-url}#assembly-install-rhdh-ocp[{installing-on-o
 
 .Procedure
 
-* To access the data from the JSON files, add the following code to the {product-short} `app-config.yaml` configuration file:
+* To access the data from the JSON files, add the following code to the `{my-app-config-file}` {product-short} configuration file:
+
+* Add the following code to the `{my-app-config-file}` file:
 +
 [source,yaml]
 ----
diff --git a/modules/customizing-the-tech-radar-page/proc-customize-rhdh-tech-radar-page.adoc b/modules/customizing-the-tech-radar-page/proc-customize-rhdh-tech-radar-page.adoc
diff --git a/modules/dynamic-plugins/con-install-dynamic-plugin-helm.adoc b/modules/dynamic-plugins/con-install-dynamic-plugin-helm.adoc
diff --git a/modules/dynamic-plugins/proc-export-third-party-plugins-rhdh.adoc b/modules/dynamic-plugins/proc-export-third-party-plugins-rhdh.adoc
diff --git a/modules/dynamic-plugins/ref-example-dynamic-plugin-helm-installations.adoc b/modules/dynamic-plugins/ref-example-dynamic-plugin-helm-installations.adoc
diff --git a/modules/installation/proc-configuring-an-rhdh-instance-with-tls-in-kubernetes.adoc b/modules/installation/proc-configuring-an-rhdh-instance-with-tls-in-kubernetes.adoc
diff --git a/modules/installation/proc-deploy-rhdh-instance-eks.adoc b/modules/installation/proc-deploy-rhdh-instance-eks.adoc
diff --git a/modules/installation/proc-deploy-rhdh-instance-gke.adoc b/modules/installation/proc-deploy-rhdh-instance-gke.adoc
diff --git a/modules/installation/proc-rhdh-deploy-aks-operator.adoc b/modules/installation/proc-rhdh-deploy-aks-operator.adoc

Original file line number	Diff line number	Diff line change
@@ -93,7 +93,7 @@ name::: `rbac-policies`
`93`	`93`
`94`	`94`	. Update your {product-short} `{my-app-config-file}` configuration file to use the `rbac-policies.csv` and `rbac-conditional-policies.yaml` external files:
`95`	`95`	`+`
`96`		-.`app-config.yml` fragment
	`96`	+.`{my-app-config-file}` file fragment
`97`	`97`	`[source,yaml]`
`98`	`98`	`----`
`99`	`99`	`permission:`
Original file line number	Diff line number	Diff line change
`@@ -25,7 +25,7 @@ plugins:`
`25`	`25`	`See link:{installing-and-viewing-dynamic-plugins-url}[{installing-and-viewing-dynamic-plugins-title}].`
`26`	`26`
`27`	`27`	`. Declare policy administrators to enable a select number of authenticated users to configure RBAC policies through the REST API or Web UI, instead of modifying the CSV file directly.`
`28`		-The permissions can be specified in a separate CSV file referenced in the `app-config-rhdh` ConfigMap, or permissions can be created using the REST API or Web UI.
	`28`	+The permissions can be specified in a separate CSV file referenced in your `{my-app-config-config-map}` config map, or permissions can be created using the REST API or Web UI.
`29`	`29`	`+`
`30`	`30`	To declare users such as _<your_policy_administrator_name>_ as policy administrators, edit your custom {product-short} ConfigMap, such as `app-config-rhdh`, and add following code to the `{my-app-config-file}` content:
`31`	`31`	`+`
Original file line number	Diff line number	Diff line change
`@@ -15,7 +15,7 @@ You can add an existing template to your {product} instance by using the Catalog`
`15`	`15`
`16`	`16`	`.Procedure`
`17`	`17`
`18`		-* In the `app-config.yaml` configuration file, modify the `catalog.rules` section to include a rule for templates, and configure the `catalog.locations` section to point to the template that you want to add, as shown in the following example:
	`18`	+* In the `{my-app-config-file}` configuration file, modify the `catalog.rules` section to include a rule for templates, and configure the `catalog.locations` section to point to the template that you want to add, as shown in the following example:
`19`	`19`	`+`
`20`	`20`	`[source,yaml]`
`21`	`21`	`----`